It can be a steep learning curve and the outcome usually reflects what goes into that first. MS has made it so that it's like giving your 14 year old the keys to the car. No doubt they will get something started, but the results will not always be pretty. Here's some of what I consider to be very important reading material, which unlike videos, you can easily put aside part way through.
Normalization is paramount. Diagramming maybe not so much for some people.
Normalization Parts I, II, III, IV, and V
http://rogersaccessblog.blogspot.ca/...on-part-i.html
Entity-Relationship Diagramming: Part I, II, III and IV
http://rogersaccessblog.blogspot.ca/...ng-part-i.html
How do I Create an Application in Microsoft Access?
http://rogersaccessblog.blogspot.ca/...cation-in.html
Important for success:
One source about how to name things - http://access.mvps.org/access/general/gen0012.htm
What not to use in names - http://allenbrowne.com/AppIssueBadWord.html
About Auto Numbers
- http://www.utteraccess.com/wiki/index.php/Autonumbers
- http://access.mvps.org/access/general/gen0025.htm
The evils of lookup fields - http://access.mvps.org/access/lookupfields.htm
Table and PK design tips - http://www.fmsinc.com/free/newtips/primarykey.asp
Multi-value fields http://allenbrowne.com/Access2007.html (in short, don't use them): quote from Allen Browne
"The relational structure behind multi-valued fields is not accessible.
Developers will find it harder to handle complex data types. Any generic procedure you write must be capable of handling fields that contain fields. You cannot use a table with a multi-valued field in an IN clause (i.e. in another database.)
Problems with filters - kb 926701"
Last edited by Micron; 01-23-2017 at 09:42 AM.
Reason: grammar
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.