Greetings, Has anyone started working on an abstraction of the new member forms? Some of the values on the lists appear to be hardcoded into the pages/templates. It would seem useful to allow a per-setup(institution) list of Town names, and localities, perhaps a list of valid Areacodes for members of the institution. It seems to me this would be best done as a small set of tables rather than in the templates themselves. My own background should illustrate my biases here: I work for a system in an urban region of about 2 Million people; my own city, the nominal "capital" of the region is about 500,000. The library I work in has 22 branches within our city, and extensive lending arrangements throughout the larger region. A new patron will register with our system in the context of a primary agency, their "local" branch. The branch records should be accessible for linking into the new patron record as a foreign key, and for display during the registration process. Further, pattern matching logic could be used against postal codes, which are nationally administered, and uniquely identify a neghbourhod (even down to a specific block). In the administrative area, a new branch would be "created" including postal area and contact info. Is any of this making sense ? Cheers, Erik Stainsby Modern Alchemy