Thread: Table Design
View Single Post
Old February 9th, 2005, 01:38 PM
Jeff Boyce
external usenet poster
Posts: n/a


You've not really given us much to go on. "Each record is a day". What
facts are you recording about "a day"?

"5 people that could access the record... editing a different field". That
may be, given your current data design. But without some idea of what you
are recording...

I'd offer a blanket suggestion against using one table per person -- as soon
as you start embedding data (i.e., which person) in your table names, you
are in trouble as far as making efficient use of Access goes. For example,
what would you do if someone new was hired? Someone was fired?

More info, please ...

Jeff Boyce
Access MVP

"Paul Cooper via" wrote in
message news:[email protected]
I'm designing an access 2003 DB for a small Newspaper. It will monitor

deadlines of the newspaper. Each record is a day. There are 5 people that
could access the record at the same time. Each person editing a different
field. Each user is forced to only edit their fields. Is it better to

1 table, or 1 for each user, and then use a relationship to connect them
together. I would prefer 1 table for simplicity, but that might not be the
best design.


Message posted via