My intuition here: You are never sure about the format of the address that will be provided. Please, look at http://www.viafox.nl/articles/Introduction%20to%20the%20Condes%20Address%20Model.html and tell me whether or not it contains some inspiration for your case.

>Hello everybody.
>
>In my app i want to provide a 'soft' address verification. what i mean with soft - its more of a recomandation rather then 'must be this way or the highway'.
>
>i am trying to think of a good flexible approach and logic and have some problems with it. here are some of the points:
>
>- at this time costly solutions are not an option
>
>- extract 'verified' address from a website like maps.google or geocoder.us and once verified add this to a local table for future speed lookup. (speed might be an issue here, also i am not sure, if this would be a good verification, and/or filling in the missing stuff)
>
>- dbf size. if working with a self-learning table (i must always keep the option of free fox tables), a verification table could grow over 2GB - problem there, even a bought dbf would give me a size problem.
>
>- option for user to choose from a list of addresses based on values already enetered. like user enetered USA, city, and zip - a list pops up and shows all streets in that zip - or something simular to that.
>
>- the whole thing needs to be at a speed which is acceptable for data entry
>
>- at this time only USA is needed but in future other countries are desirable
>
>- this verification should add missing stuff, like "### MyStreet" + "Dr."
>
>anyone got some ideas on this?
>any pointers/help are greatly appreaciated.