Limitations on WHERE Clause in lookup query for a table column

[jimthompson5802]

I have a Access Table with two columns. Each column is defined a lookup
column with an underlying SQL query.

When a user selects a value for Column A, I'd like the lookup query in
Column B to show only values related to the value chosen for Column A. In
other words, I'm trying to code something like,

SELECT OtherTable.AttrX FROM OtherTable WHERE OtherTable.AttrY = ColumnA;

I can't seem to get the WHERE clause to recognize the value chosen for
Column A for the specific row of data being modified.

Is this a limitation of a lookup query in Access or I'm just missing
something?

Jim T

 

[Larry Daugherty]

Stop!

Lookup fields in tables are a miss-feature provided by Microsoft that
should never be used - ever! For a discussion see
www.mvps.org/access search for "lookup field"

Tables are simply for the storage of data. Fields must be "atomic" in
that they store a single value of a single type. Keep to the
traditional rules of Normalization. Avoid "lookup fields" and
"multi-value fields". Their use leads to lots of frustration, extra
work, even abandonment of Access.

Note that "Lookup tables" are good things. Lookup Tables are simply
regular tables that hold lists of values for use by other parts of
your application.

HTH