Storing Address Details in a Table
When you come to creating a database that will be storing addresses and names, of people, you need to decide how your database is going to deal with this data. Is it going to treat the address as one object, and never do anything with it apart from printing it is a 'blob' in which case you would just have an Address field, or are you going to want to know how many customers live in a certain town, in which case you are going to want to have several address fields. It is far easier to get this design right from the start, than to have the user change their mind after using the application for 6 months, with several thousand addresses already entered in.
If you do decide to store the data as one blob, and then decide that you really need it separated, you will need to run some update queries on the data, and be prepared for some manual checking and tweaking.
Obviously, once you have successfully split your data into the component parts, you will need to look at using concatenation to join them back up again in reports.
Top
HOME |
NEW |
TABLES |
QUERIES |
FORMS |
REPORTS |
GENERAL |
API |
DOWNLOADS |
TUTORIAL |
RESOURCES
E-MAIL
Copyright & Disclaimer
| 
