If there are a variable number of users there needs to be a related Users
table. Eight separate fields is a poor design, even if you never have nine
users and need to redesign the database.

The structure is not clear. Are there offices and officers? Are the users
offices or officers?

Whatever they are, an Organization may have several of them, so there is a
one-to-many relationship between Organization and Users, which means there
needs to be a related Users table. Its foreign key is linked to the primary
key of the Organization table.

If an organization has several users, how can an organization be a user? The
business logic eludes me.

Please note Karl's response for more thoughts.


Ron A. wrote:
I forgot to say that the usercode 1 thru 8 in the tblOrg are foreign Keys
from tblUsers/UserID. I did this becaue 1 Orginization can have many users
within it.
Let me try and shed more light. Units may be misleading, so let's call them
orginizations. An orginization (Org) is assigned a master org code and all of
[quoted text clipped - 130 lines]
I hope I gave enough info and thanks for taking the time to dredge
through this.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...esign/201004/1