A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

auto populating



 
 
Thread Tools Display Modes
  #1  
Old May 19th, 2004, 05:08 PM
Ryan
external usenet poster
 
Posts: n/a
Default auto populating

Hello,

not sure how to do this but what I need to do is have one
table get info for a field by pulling information from 2-
3 other fields and then use this new field as the link
between tables.

Is this possible
  #2  
Old May 20th, 2004, 02:34 AM
Jeff Boyce
external usenet poster
 
Posts: n/a
Default auto populating

Ryan

Good relational database design frowns on building a composite field
("information from 2-3 other fields). If you need a field (or fields) to
serve as a key to another table, there are a couple approaches.

One would be to include as many (key) fields in the related table as you
have in the primary table.

Another would be to add an autonumber primary key field to the primary
table, and use THAT as your key "relating" field in the secondary/related
table.


--
Good luck

Jeff Boyce
Access MVP

  #3  
Old May 20th, 2004, 06:39 AM
John Vinson
external usenet poster
 
Posts: n/a
Default auto populating

On Wed, 19 May 2004 09:08:05 -0700, "Ryan"
wrote:

Hello,

not sure how to do this but what I need to do is have one
table get info for a field by pulling information from 2-
3 other fields and then use this new field as the link
between tables.

Is this possible


It's a VERY BAD IDEA. Yes it's possible, but it is neither necessary
(to do what you describe) nor wise.

Note that you can use up to TEN fields as linking fields in a Query.
You don't need to store data redundantly in order to do this. Or, you
might do better to add a unique field as a primary key in one of the
tables (an Autonumber if you don't have a good natural key) and use a
compatible foreign key in the other table (Long Integer if you use an
autonumber); you would then use a Query to link to the first table to
retrieve these two or three fields rather than storing them
redundantly.

John W. Vinson[MVP]
Come for live chats every Tuesday and Thursday
http://go.compuserve.com/msdevapps?loc=us&access=public
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 11:42 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.