Large Table

[Birdman895]

Hi,
I am creating an Access app for a non-profit organization that offers treatment to patients. On a patients first appointment they have to fill out paperwork to provide general info, family history, medical history, financial info, plus a couple more.
I will end up with a table with 150-200 fields. Would it be a good idea to break this up into seperate tables along topical lines? Even though they would be 1-to-1 relationships?
Thanks
alan

 

[PNGBill]

The number of fields isn't really a reason to have additional tables. What data the fields hold is the issue.

When you say One to One relationship, you may need to rethink.

Medical History shouldn't be One to One. This could well be a seperate table, tblMedicalIssues and you use a Junction Table to keep track of who has what condition and or what family history.

Even Residential Address can be a seperate table, if you wish. This way, tblPatient has one field for residential address rather then 5 ot 6.

Just depends how far you wish to take it but 150 fields does seem like you have some room for additional tables.

Check Database Normalisation for a full story.

 

[Birdman895]

Thanks a lot for the answer. Your input helped and so did the videos on normalization that you gave me a link for.
I'm sure I'll be here a lot.
alan