Table Design

[Denise Walker via AccessMonster.com]

I'm looking for the best design for a database I'm creating.

I have a table that has 60 fields. The User wants to be able to bring up
client records that only use certain fields that pertain to that client.
One Client may only use 12 fields were another Client may only use 4 fields
and another Client may use 20 fields from this table.

Also, This 60 field table will be used by 3 small User groups which will
need to access similar sets of data at different times. No more that 12 to
15 users updating this table at one time. More (around 50 may be
previewing the data only)

1. Should I break up this large 60 field table into smaller tables with
logical groupings (client name address table, candidate table, background
verification table, skill table, rate table, etc.) and tie them all to a
primary key such as (client name, client id)?

2. If so, how would this affect the User groups accessing the table. I
would like the forms to load fast for them.
3. Or is it better just to run queries off this large table for faster form
performance.

Thanks in advance for your help!
Denise

 

[Duane Hookom]

I would think this is more appropriate for the tablesdbdesign news group
where you have already posted the same question. If you can't find your
posting in the other News Group, it might be due to the undescriptive
Subject. Anyone looking through the tablesdbdesign NG would expect questions
to relate to "Table Design".