Ok, you just scratched the surface on detailing your needs.

I have seen people create a fixed design database where there is exactly
one field that holds street name and number, another field that handles
city etc.

This type of design is perfect for an evironment that is static. It
quickly breaks down once someone asks to hold rural road and lot numbers
in the table - or you get more phone numbers than were origionally
designed for.

I have seen another design that had the database contain a single table,
and that table only had 6 fields. That database could hold any type of
address and in fact any kind of data you wanted to hold ( level 5
normalization with many to many links)

Please detail the compleate environment you are in and where you have
grey areas that can be addressed.

best regards

Dalton

Jannie Nel wrote:

> >>What problems are you having?
> >>Alot of companies use firebird for even larger volumes of data than
> >>you are describing.
>
>Hi Dalton,
>
>We are looking at open source databases for an upcoming project. They
>will require fairly extensive search capabilities on person information
>- by area, street, etc.
>
>My other option so far would be MySQL, but because we are a Delphi shop,
>I'd prefer FireBird.
>
>Jannie.
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
>