Art-
You need two tables, and the only thing redundant should be the linking key -
probably ClientID. The "main" table could actually be the account that
represents the client, with a link on AccountID to Account Members. The Account
Members table would hold both the client (with a flag to indicate the person in
the record is the account holder) as well as household members. I would need
more details about the specific data you need to track to give you a more
definitive answer.
John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)
-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com
[mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Art
Sent: Thursday, October 06, 2011 5:36 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Single table for client and household
Does any one have an idea on how can develop a single table that would contain a
client data as well as household members data? It would need to demographic data
for the client (name, address, dob, ssn, etc) and as well as for household
members.
I thought o do it in two seperate tables but that would lead to redundant data
in both the client table and the household member table for the client record.
If there was sample somewhere for me to look at it would be great.
Thanks
Art Lorenzini,
Sioux Falls, Sd
------------------------------------
Yahoo! Groups Links
Tidak ada komentar:
Posting Komentar