Probably not, but you're not close to worrying about that yet. I'm just going to copy/paste from a list I have; might be some repetition here. One of the more important aspects is to grasp the entity/attribute relationship. 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
and/or
http://holowczak.com/database-normalization/
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/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
About calculated table fields -
http://allenbrowne.com/casu-14.html
Be sure to check this out; lots of links in post 3 and good comments throughout the thread
https://www.accessforums.net/showthread.php?t=65220
I have been playing around in the meantime and might as well post what I have rather than save or lose it. I'm sure there's a mistake or two as now I'd have to go back and review your comments regarding the way thing work. Sorry, cannot seem to control the individual table column widths.
First 3 should be obvious. They're lookup tables (not lookup fields); basically an entity list.
tblPatients |
|
PatientIdPk |
|
FName |
|
Lname |
|
etc. |
- pertaining to patient data |
tblCareProviders |
|
CpIdPk |
|
ProviderType |
*don't use Type |
PTypeDesc |
*don't use Description |
FName |
|
Lname |
|
etc. |
|
tblSessions |
- list of 6 (currently) session types |
SessionTypePk |
|
SessionName |
*don't use TypeName |
tblPatientMtgs |
|
PmtgIdPk |
|
PatientIdFk |
- allows multiple meetings per patient |
etc. |
-such as location, date, start/end times |
tblMtgCareProv |
- which care provider(s) attended meeting? |
MtgCpPk |
|
PmtgIdfk |
- patient meeting ID; allows multiple session recommendations for a meeting |
SessionTypefk |
- what session recommended by (next field) |
CpIdfk |
- from tblCareProvider - who recommended the session |
etc. |
- pertaining to session; e.g. start/end times |
That's it for tonight; boss is calling me. Dog wants out too...