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

[Colin]

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

[Colin]

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

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.


colin.m@sympati co.ca (Colin) wrote in message news:<658c1d2f. 0404160910.2138 7664@posting.go ogle.com>...[color=blue]
> 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[/color]