By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,379 Members | 3,035 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,379 IT Pros & Developers. It's quick & easy.

Lookup Help

P: 2
Hi Guys and Gals,

Basically, I need some help im stuck on the most Simplist of Things and it is doing my Nut.

I have 2 Tables -

TblCustomers
and
Tbl Phonecalls

Both tables have the same CustomerReference number on them

Now what i need is to Be able to Let the TblPhoneCalls Table Has the Exact same Colum as TblCustomer into the Othertable... So when my VBA is updating TblCustomers i want TblPhoneCalls to update the Data for the Few Selected customers Already there.

I was told this was Possible With a Lookup... All i can get that to do is create a drop down menu where i can Select Data From

Thank in Advaced

Ralph
Nov 23 '06 #1
Share this Question
Share on Google+
4 Replies


NeoPa
Expert Mod 15k+
P: 31,494
Ralph,

It's not a good idea to store the same data in two separate places EXCEPT the data that links from one table to another (or FK).
Avoid updating to match, simply store in one place and link the tables together in a query to show the related data.
Nov 23 '06 #2

P: 2
So you are suggesting an Update query?

Or just run a Query? And use the query as the readable data?

Cheers Mate

Ralph

Ralph,

It's not a good idea to store the same data in two separate places EXCEPT the data that links from one table to another (or FK).
Avoid updating to match, simply store in one place and link the tables together in a query to show the related data.
Nov 23 '06 #3

NeoPa
Expert Mod 15k+
P: 31,494
So you are suggesting an Update query?

Or just run a Query? And use the query as the readable data?
Cheers Mate

Ralph
Definitely the latter (highlighted).
Nov 23 '06 #4

nico5038
Expert 2.5K+
P: 3,072
As stated, storing twice the same data isn't OK. It's called data redundancy and against the normalization rules.
Just imagine that the tblCustomers is changed and you forget the tblCalls. Afterwards it's impossible to tell which of the fields is correct when you can't trace who and when the field has been changed...

As I assume that a ReferenceNumber is a property of a Customer, it's best to keep the field there.
When you need customer information combined with the calls, just create a query to show the data by joining the tables.

When there can be multiple calls per customer you might use a "master" form for the customer and a subform for the calls. The Access subform wizard will propose a filtering you can accept and only the calls of the customer will show in the subform. Same idea as the Order and OrderDetails in the NorthWest.mdb sample database that comes with Access.

Clearer ?

Nic;o)
Nov 23 '06 #5

Post your reply

Sign in to post your reply or Sign up for a free account.