Relationshsips
  Home FAQ Contact Sign in
 
Advanced search
MATCHING GROUPS



more...
POPULAR GROUPS

more...

found 5 articles for 0.302 sec
Hi This is one method Create 2 tables called tblQuestions and tblAnswers tblQuestions QuestionID Autonumber Question Text tblAnswers AnswerID Autonumber QuestionID number Answer Text This is a good idea as you may (now or in the future) have a question with more than one answer and it is "always" a good idea (if pos) to create a database that will easily expand     

Group: microsoft.public.access.gettingstarted · Group Profile · Search for Relationshsips in microsoft.public.access.gettingstarted
Author: Wayne-I-M
Date: May 4, 2008 23:14

That certainly is one way of setting up a 1-to-many relationship, yes -- assuming that the autonumber field is the primary key in the "parent" table. Be sure to set the data type of the AcctID field in the "child" table to Number - Long Integer. -- Ken Snell <MS ACCESS "jk" <jk@discussions.microsoft.com> wrote in message news:F4F41631-76CB-4B2C-8838-433BAD1C2F05@microsoft
Show full article (1.39Kb) · Show article thread
To be clear on this, the autonumber is the primary key and the AcctId is the foreign key in the account table? "Ken Snell (MVP)" wrote: > If each invoice record can have only one account number, then you have a > one-to-one setup for that record. You should be able to use the AcctID value > in the ACCTS field, where AcctID is a foreign key to the primary key in the > Accounts table. No     

Group: microsoft.public.access.tablesdbdesign · Group Profile · Search for Relationshsips in microsoft.public.access.tablesdbdesign
Author: Ken Snell (MVP)
Date: Apr 20, 2007 13:04

If each invoice record can have only one account number, then you have a one-to-one setup for that record. You should be able to use the AcctID value in the ACCTS field, where AcctID is a foreign key to the primary key in the Accounts table. No need for another autonumber field here. -- Ken Snell <MS ACCESS "jk" <jk@discussions.microsoft.com> wrote in message news:20DCD8A7
Show full article (1.76Kb)
I am developing a database to monitor the expense's of five differnt company locations which have a ubique 3 digit identifier number. The invoices genereated from each location have a unique invoice number so that will be the one to many relationship. The invoices can only have one expense account per invoice but i am unsure if this should be a one to one relationshsip or one to many. The     

Group: microsoft.public.access.tablesdbdesign · Group Profile · Search for Relationshsips in microsoft.public.access.tablesdbdesign
Author: jk
Date: Apr 20, 2007 07:44

Show full article (1.30Kb)
    

Group: microsoft.public.access.tablesdbdesign · Group Profile · Search for Relationshsips in microsoft.public.access.tablesdbdesign
Author: Ken Snell (MVP)
Date: Mar 18, 2007 09:14

Show full article (1.09Kb) · Show article thread
    

Group: microsoft.public.access.tablesdbdesign · Group Profile · Search for Relationshsips in microsoft.public.access.tablesdbdesign
Author: jk
Date: Mar 17, 2007 21:34

Show full article (0.61Kb)