lookup fields

[Kenny]

I followed a link from this forum to the access web and found the 10
commandments of Access and number 2 was to abhor the use of lookup fields.
I followed the link and it explained why they were bad, but didn't say what
you should use instead.
What is the acceptable way to get the same good direct effect without the
bad side effects?
Thanks,
Ken

 

[John Vinson]

What is the acceptable way to get the same good direct effect without the
bad side effects?

Use "Lookups" - also known as Combo Boxes - on a Form, and avoid ever
using table datasheets for any purpose other than debugging.

There's nothing wrong with looking up values in another table, in fact
it is universally used. What's wrong is Microsoft's misleading,
misdesigned, and all but useless so-called "Table Lookup Wizard".

 

[Matthew Therrien]

Hello John
Your comment on the Lookup Wizard interested me. What's
wrong with it and what should one do instead to lookup a
related field value ? It works ok as far as I see but then
I am a relative newbie

Matthew

 

[Rick Brandt]

See http://www.mvps.org/access/lookupfields.htm for a detailed
description.

One of my concerns about them is that they *encourage* the use of
table datasheets for routine data manipulation, a task which is far
better performed by Forms.

I've always thought that the way SQL Server Enterprise Manager exposes tables in
version 6.5 was the proper way. All you can see about tables are the design
attributes. If you want to see *data* you have to write a query.

I think it especially true for a tool that is often used by those unfamiliar with
database concepts (like Access) that this conveys the proper idea that whenever you
retrieve data, a query is always being used. Opening tables directly (which still
executes an internal query) just blurs the issue.