G
Guest
I want to have the same data in two different tables. (ex. user id).
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
D
Dan Artuso
Please, try to explain your problem adequately.
People here are willing to put the time in to help you if you are willing to put the time in to explain your problem.
People here are willing to put the time in to help you if you are willing to put the time in to explain your problem.
G
Guest
Dan, sorry about that I was a little quick with the post tab.
Ok here it goes:
Talbe A (user id, pc name, os type) along with other info
Table B (user id, pc name, os type)
I want to elimante having to type the same info over and over, so if I type
the info in Table A, I would like it to be automatically in Table B. I don't
have any Relationships set since that isn't the proper way to construct the
Database. Hope this is clear enough, any suggestions will be helpful.
Ok here it goes:
Talbe A (user id, pc name, os type) along with other info
Table B (user id, pc name, os type)
I want to elimante having to type the same info over and over, so if I type
the info in Table A, I would like it to be automatically in Table B. I don't
have any Relationships set since that isn't the proper way to construct the
Database. Hope this is clear enough, any suggestions will be helpful.
D
Dan Artuso
Hi,
Okay, I don't know where you got the idea that relationships are not the way to go, beacuse they are.
Although in this case it seems that you are simply duplicating your table structure and data.
Is there a reason you are not simply storing all the data in one table?
If table B actually has other fields besides the ones it has in common with table A, then you simply want to store the userid
in table B and nothing else.
Okay, I don't know where you got the idea that relationships are not the way to go, beacuse they are.
Although in this case it seems that you are simply duplicating your table structure and data.
Is there a reason you are not simply storing all the data in one table?
If table B actually has other fields besides the ones it has in common with table A, then you simply want to store the userid
in table B and nothing else.
G
Guest
Okay, but now your post makes no sense to me. Table A has other fields, so
does table B, that is why I need two tables...but I also don't want to
re-enter the same info...so my question is how do I go about doing that?
does table B, that is why I need two tables...but I also don't want to
re-enter the same info...so my question is how do I go about doing that?
G
gls858
Al said:Okay, but now your post makes no sense to me. Table A has other fields, so
does table B, that is why I need two tables...but I also don't want to
re-enter the same info...so my question is how do I go about doing that?
:
Any time you have duplicate info in two or more tables your databse is not
normalized. The whole point of having a relational database is to NOT
have duplicate info. You basic design is flawed. You need to check out some
articles on normalizing data. Here's just one link. there are many others
if you google on mormalize data.
http://www.accessdatabasetips.com/normalizing-data.html
D
Dan Artuso
Hi,
Well, the answer is... you don't. There is never any need to enter duplicate info.
The idea is that tables will have relationships with one another. One table will have a primary key and the
other table will have that same value stored in it as a foreign key. The relationship is usually a one-to-many.
This will almost always be presented as a main form/sub form with the linking fields being the
primary and foreign keys. Access will then take care of inserting the foreign key into table B without any
user intervention.
Well, the answer is... you don't. There is never any need to enter duplicate info.
The idea is that tables will have relationships with one another. One table will have a primary key and the
other table will have that same value stored in it as a foreign key. The relationship is usually a one-to-many.
This will almost always be presented as a main form/sub form with the linking fields being the
primary and foreign keys. Access will then take care of inserting the foreign key into table B without any
user intervention.
G
gls858
gls858 said:Any time you have duplicate info in two or more tables your databse is not
normalized. The whole point of having a relational database is to NOT
have duplicate info. You basic design is flawed. You need to check out some
articles on normalizing data. Here's just one link. there are many others
if you google on mormalize data.
http://www.accessdatabasetips.com/normalizing-data.html
this is probably a better link the one above doesn't go into much detail.
Watch for line wrap
http://www.fmsinc.com/tpapers/datanorm/#Data Normalization Overview
gls858