People who have asked for help admitted that when they created their databases they had not give enough thought to its foundations - to the stage of database design referred to as “data modelling”. You will also need to assess your skills levels in respect to how much you know about working with MSA, and to assess what time you can spend on the development of your database. Hence this article.īefore launching into its construction, I recommend you allot time for considering what purpose your database is to serve and, were it to prove a triumph, what development it might benefit from in the future. If you construct a contacts DB properly from the outset, then extending it, or incorporating it as a module into any future database you plan, will save you a lot of time and possibly a lot of expense.
Of those I’ve seen, I considered none was fully fit for what I wanted. There are templates for DBs (databases) that come with your purchase of MSA (Microsoft Access) and others that are available off the web. The majority of databases I’ve worked on over the decades have held information about contacts: names and addresses, telephone and mobile numbers, and email addresses.
If you haven’t given data modelling any consideration, then Data Modeling in Practice is worth a read before starting your contacts database. It may be satisfactory for what you have in mind for your database, but before adopting it as is, see Possible Shortcomings of This Data Model.
Please consider critically the data model proposed in this article. How to structure Microsoft Access tables for an contacts management database that also acts as a module to include in your other databases that need to track contacts.
0 kommentar(er)
