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

Lookups - What's Best...In a Table or on a Form?

P: n/a
Question#1:
Many of my forms have combo boxes (e.g. CustomerID). The combo box
looks up CustomerName from CustomerID in the Customer table. Am I
better off including CustomerName in my query (which the form depends
on)and have the combo box based on CustomerName or is it better to
limit the query fields by using just CustomerID? I'm guessing that
keeping queries to a minimum will impact the speed in which queries
take place.

Questions#2
Is it better to design the lookup on the form or originate it from the
table?

Thanks
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I think I can answer the second question. It appears to be better
originating lookups from the form.
As for the first question. The PK used as a combo box lookup works
fine for selecting a record but not changing one as you end up trying
to change the PK.
co*****@sympatico.ca (Colin) wrote in message news:<65**************************@posting.google. com>...
Question#1:
Many of my forms have combo boxes (e.g. CustomerID). The combo box
looks up CustomerName from CustomerID in the Customer table. Am I
better off including CustomerName in my query (which the form depends
on)and have the combo box based on CustomerName or is it better to
limit the query fields by using just CustomerID? I'm guessing that
keeping queries to a minimum will impact the speed in which queries
take place.

Questions#2
Is it better to design the lookup on the form or originate it from the
table?

Thanks

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.