A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Limitations on WHERE Clause in lookup query for a table column



 
 
Thread Tools Display Modes
  #1  
Old December 18th, 2009, 04:21 PM posted to microsoft.public.access.tablesdbdesign
jimthompson5802
external usenet poster
 
Posts: 2
Default Limitations on WHERE Clause in lookup query for a table column

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
  #2  
Old December 18th, 2009, 04:43 PM posted to microsoft.public.access.tablesdbdesign
Larry Daugherty
external usenet poster
 
Posts: 1,012
Default Limitations on WHERE Clause in lookup query for a table column

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

--
-Larry-
--

"jimthompson5802" wrote in
message ...
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



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 04:14 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.