I agree that it's not so useful for working with the table and queries. But,
setting the lookup properties makes that the default when a field is added
to a form. It is convenient to have a combo box generated automatically with
all the properties setup correctly. So I often do set the lookup properties,
just for that purpose. And it's convenient when looking at a table
datasheet, which is something only the developer should be doing, not users.
If you want to see the id value in a query, you can use TheID: id + 0 as a
column expression.
"Denise" <(E-Mail Removed)> wrote in message
news:1B584275-C97E-4CCE-B158-(E-Mail Removed)...
> Thank you once again. While I was waiting for a response, I tried using
> and
> could quickly see that this was not going to work. I will restart ignoring
> lookup tab.
>
> "John Spencer" wrote:
>
>> The general consensus is that it is a bad idea.
>>
>> Why? It tends to hide the real data from the user (and the designer).
>> Although the displayed value might be "William Shatner", the actual
>> stored value might be 11. So now when you build sort things aren't
>> necessarily in alphabetic order and when you search you need to search
>> for 11 and not for "William Shatner" or Like "*SHA*".
>>
>> It can be useful, but you had better be aware of the limitations it
>> imposes. And as far as I can tell, it simply does what you would do
>> anyway. Those values that are available have to come from somewhere and
>> that usually means a table has been created and populated.
>>
>> '====================================================
>> John Spencer
>> Access MVP 2002-2005, 2007-2009
>> The Hilltop Institute
>> University of Maryland Baltimore County
>> '====================================================
>>
>>
>> Denise wrote:
>> > Is it recommended in the dbs table design to use lookup tab and to
>> > select
>> > either list or combo with row source?
>> > Why or why not?
>> > Thank you
>>
|
Similar Threads
