From: John W. Vinson on
On Sat, 14 Nov 2009 05:59:01 -0800, .:RoKsTaR:.
<RoKsTaR(a)discussions.microsoft.com> wrote:

>So I watched crystals video and went through some of the other material and
>have been noodling around with the program and existing databases to help
>figure things out. In crystals video, she talks about putting people,
>addresses, and phone numbers in their own table and linking them by their
>unique id or key number. Existing templates do this all in one table, whcih
>to me makes data entry easier, but I'm not sure.

One table makes data entry easier... but is also more limited. Some people use
more than one address; many people use more than one phone (home, office,
mobile for example). It's a judgement call based on how the database will be
used - some databases will be fine with one table (with its limitations),
others may need separate tables.

>Can anyone clarify if separate tables would make the data entry portion more
>time consuming? Can you have one form that enters data into many tables?

Sure. A Form based on Contacts with Subforms based on the Address and Phone
tables. There'll actually be three forms, but they'll all be onscreen and
editable at the same time.

>Side note : A friend of mine told me he can get me some training dvds from
>his office library, so I think that's my next step ;)

If they're good ones....

--

John W. Vinson [MVP]
From: .:RoKsTaR:. on
I talked to him yesterday and he said that he can get me something called
trainsignal from their library. He says it's pretty intense and he thinks
his company used it to certify some employees for access...does that sound
right?
From: .:RoKsTaR:. on
He says it something called trainsignal, but didn't know much about it. From
what I can tell, it looks pretty thorough :)
From: .:RoKsTaR:. on
Whoops ;) I dind;t think that first post showed up so I did another
one...sorry ;)
From: Fred on
I have not watched Crystals (even through she is an Access teaching goddess)
but I suspect that you misinterpreded something from it, and, either way, you
post indicates that you have yet to really understand the important
foundation items.


(The table design that ends up as ) linking tables is to to properly handle
"one to many" and "many to many" type relationships between the entities that
you are databasing.

If the entity that you are databasing in your address book is just People
(i.e not organizations, companies, etc. lists of coins that those people
own ) chances are that putting all of their info into one table (i.e. not
separate linked tables) is the best way for you to go.