Hopefully very simple relationship/table/form question

[al_mac75]

I have a hopefully very simple question for a problem that I haven't
been able to work out. I have a very simple database to record client
accounts and therefore have a table called Accounts. I have one client
that needs some additional information populated every time a new
account record is added. The simple way to do this would just be to add
these fields to the Accounts table; however, I am really looking for a
way to do this so that the information is only added for this
particular client and is always added an any new records. I have set up
another table but can't figure out how to format the realtionship so
that the information from the Accounts table feeds into the new table.
Can anyone assist ?

 

[Guest]

I have a hopefully very simple question for a problem that I haven't
been able to work out. I have a very simple database to record client
accounts and therefore have a table called Accounts. I have one client
that needs some additional information populated every time a new
account record is added. The simple way to do this would just be to add
these fields to the Accounts table; however, I am really looking for a
way to do this so that the information is only added for this
particular client and is always added an any new records. I have set up
another table but can't figure out how to format the realtionship so
that the information from the Accounts table feeds into the new table.
Can anyone assist ?

The Accounts table really shouldn't "feed" the new table - that would imply
that you're storing data redundantly, always a bad idea. For that matter if
you're adding *the same* information every time, that's redundant too!

If the information is related to Accounts but only to one (or a few)
accounts, you have a good example of "subclassing" - the one common reason
for the otherwise rare one to one relationship. Make your new table with the
AccountID (the primary key of Accounts) as its Primary Key, and create a
relationship joining Accounts.AccountID to this primary key. Access will make
it a one to one relationship. You can set the Default Value property of any
of these fields however you like, and put a subform on the form where you
enter account information. Entering any data into the subform will create a
new record in this table.

If this isn't clear, please post back and explain the nature of this data
and why you need a new record for every account.