David-
You could do a 1-1 relationship. To do that, make sure that the same field is the Primary Key of both tables. One table (the one with the 4 universal fields) will be the "parent" table, and the other the "child." When you use the same unique value in two tables in a relationship, Access will recognize the 1-1 relationship.
John Viescas, Author
Effective SQL
SQL Queries for Mere Mortals
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
(Paris, France)
On Dec 30, 2016, at 8:43 PM, david.pratt@outlook.com [MS_Access_Professionals] <MS_Access_Professionals@yahoogroups.com> wrote:
I have a table that has 13 fields. Of those 13 fields, four fields will be used in all of the records. The remaining 9 fields will only be used in about 50% of the records.
In this case, do I break the table up into two tables, a Parent and Child with a one:one relationship?
If I do make two tables, how do I force a one to one relationship and prevent multiple child records from being created?
Or do I just two different input forms to fill in the table?
__._,_.___
Posted by: John Viescas <johnv@msn.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
Have you tried the highest rated email app?
With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.
.
__,_._,___
Tidak ada komentar:
Posting Komentar