Re: Table Design - Relationships

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Tom (bockREMOVETHIS_at_sigmongroup.com)
Date: 02/13/04 

Date: Thu, 12 Feb 2004 19:46:05 -0500

Graham:

I now realize that I have a problem with the forms. I followed your
instructions and designed the tables as suggested.

I now wanted to use forms w/ subforms to enter the data. However, no matter
how I design the forms, I always get errors, e.g. "Forms not updatable" or
"Missing Index".

Looking at the raw tables via a combination query, all records are lined up
properly and I have the accurate count of records.

Any suggestions as to how I must string them into a form? 

-- 
Thanks again,
Tom
"Graham R Seach" <gseach@NOSPAM_pacificdb.com.au> wrote in message
news:uOHOVtb8DHA.3704@tk2msftngp13.phx.gbl...
> Tom,
>
> You just need to create links between tblFacility and tblAccount, and
> between tblAccount and tblBills.
>
> The relationships you define depend entirely on their real-world
> relationships. Can a facility have a bill without an account? Based solely
> on what you've identified thus far, the following relationships may
suffice.
>
> tblFacility
>     FacilityID 'Autonumber - Primary Key
>     FacilityName
>     '--- other columns
>
> tblAccount
>     AccountID 'Autonumber - Primary Key
>     FacilityID 'Long Integer - Foreign Key to tblFacility.FacilityID
>     '--- other columns
>
> tblBills
>     BillID 'Autonumber - Primary Key
>     AccountID 'Long Integer - Foreign Key to tblAccount.AccountID
>     '--- other columns
>
> The relationships would be:
>     tblFacility.FacilityID (many) --> tblAccount.FacilityID (one)
>     tblAccount.AccountID (many) --> tblBills.AccountID (one)
>
> Graham R Seach
> Microsoft Access MCP, MVP
> Sydney, Australia
>
>
> "Tom Bock" <bock@sigmongroup.com> wrote in message
> news:eEZsTFb8DHA.2392@TK2MSFTNGP11.phx.gbl...
> > I need some feedback w/ table designs:
> >
> > This is the structure:
> > 1. tblFacility
> > 2. tblAccount
> > 3. tblBills
> >
> > Each facility has 1 or more accounts.
> > Each account has 1 or more bills.
> >
> > What is the best way to create the relationships?   I believe I need to
> > create a junction table.
> >
> > If yes, will the junction table have all FKs to their PKs?
> > Or should I create 2 junction tables.... #1 between Facility & Account,
> and
> > #2 between Account and Bills?
> >
> > Any advice is appreciated.
> >
> > Thanks,
> > Tom
> >
> >
>
>

Relevant Pages

  • Re: Table Design - Relationships
    ... > between tblAccount and tblBills. ... Can a facility have a bill without an account? ... FacilityID 'Autonumber - Primary Key ...
    (microsoft.public.access.tablesdbdesign)
  • Table Design Architecture - Form Challenge
    ... Each facility has 1 or more accounts. ... Each account has 1 or more bills. ... Here's why I chose this main/sub form structure. ... FacilityID 'Autonumber - Primary Key ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Table Design - Relationships
    ... between tblAccount and tblBills. ... Can a facility have a bill without an account? ... FacilityID 'Autonumber - Primary Key ...
    (microsoft.public.access.tablesdbdesign)
  • compensation toward busy cult
    ... raise hitherto or Calvin will account the sufferers. ... Some abuses hand, pretend, and analyse. ... A lot of joint individual suburb realizes groupings about Hamid's ... It might delay once, underline forward, then design ...
    (sci.crypt)
  • Re: Real world modeling.
    ... >> Such alignments were possible long before object oriented languages ... >> Whenever a new kind of account is created, ... >> The result is a looser coupled design. ...
    (comp.object)