Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Database Design / July 2005

Tip: Looking for answers? Try searching our database.

Table Design

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bryan Hughes - 28 Jul 2005 20:15 GMT
Hello,

I have a db I am developing and I am at a impasse.

I have a agency table that stores a unique ID for each agency.
Each agency has multiple program names unique to an individual agency,
and each user is assigned to an agency but can be part of multiple programs
for that agency.
Should I create a single Program Table with Agency ID and a single User
table with Agency ID for all programs and users, or should I
create a user table for each agency and put the agency programs table under
this?

-TFTH
Bryan
KARL DEWEY - 28 Jul 2005 22:49 GMT
The structure below is based on a user not working for more than one agency.

tblAgency
    AgencyID (PK)
    Name
    Other data fields
   
    tblAgencyProgram
        AgencyID        (two field combination PK)
        ProgramName

        tblProgramUser
            AgencyID
            ProgramName
            User
Set relation of PK to the same field in table below it.

> Hello,
>
[quoted text clipped - 11 lines]
> -TFTH
> Bryan
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.