Hello, I'm developing a DB that will be used for operational use at a med clinic so it is heavily form dependent for non-technical users. It tracks patients as they cycle through a clinic (inputting data along the way).
Everything will need to be unique per patient appointment.
With one appointment there are well over 100 required fields.... I'm trying to split these into multiple tables even though they will all need to be updated, and modified based on the same appointment.
The thing that worries me is there are two memo fields. One of them will typically be multiple pages. I'm worried that having all of these records AND the two memo fields in the same table, while having 5-10 users modifying and editing the single table via multiple queries and forms will severely slow this DB down.
For example in one form (the one that is used to book apt) the user enters data and then copies/pastes a large memo field. I want to be able to append the data/information into two tables simultaniously but still have the same apoitment ID for both records.
I know that 1:1 relationships are dumb, but I can't think of a good way to separate out the memo or other fields as they are unique per apt. When I have a 1:1 relationship, I can't figure out how to append to both tables (for example Apt_ID is PK in both tables and has a 1:1 relationship *?Is this right/possible?*, and I want to add a Pt_Name and Vital_Signs to two separate tables)
I could really use some help...
It's been a long while since I've tried to build a DB, and nothing I've done has been this complex...
This sort of issue is heavily dependent on the database platform you are using, and my MS Access is a little rusty. I am going to move your thread to the MS Access forum, where there are folks with more experience in this matter.
If it's not practically useful, then it's practically useless.