R
rgrantz
I've looked through the Help in Access 2K, and heven't been able to wrap my
head around this:
If you have unbound control values setting the criteria in the query design
grid ([forms]![formname]![controlname]), but you also want to allow for is
Nulls in all of them, and you also want to allow for nulls in the underlying
table values, what is the rule of thumb for how to structure where the
"[formcontrolstuff] is null" and the "[table value or calculated control]"
is null are placed in teh grid?
When I set the Or cells in query design, then save the query and open it in
design view again, I notice Access makes new fields and arranges the
[formcontrol] is null and the actual field Is Null in a weird arrangement
(some Is Nulls being in the first OR row of the grid, some one row down,
some a couple rows down, etc.). I have not been able to see the rhyme and
reason Access applies to this, and I'm thinking maybe a lot of my
unpredictable query results are because I'm not using the OR rows right.
Is there some heirarchical system applied to placement of criteria in the OR
rows?
Thanks for any help
head around this:
If you have unbound control values setting the criteria in the query design
grid ([forms]![formname]![controlname]), but you also want to allow for is
Nulls in all of them, and you also want to allow for nulls in the underlying
table values, what is the rule of thumb for how to structure where the
"[formcontrolstuff] is null" and the "[table value or calculated control]"
is null are placed in teh grid?
When I set the Or cells in query design, then save the query and open it in
design view again, I notice Access makes new fields and arranges the
[formcontrol] is null and the actual field Is Null in a weird arrangement
(some Is Nulls being in the first OR row of the grid, some one row down,
some a couple rows down, etc.). I have not been able to see the rhyme and
reason Access applies to this, and I'm thinking maybe a lot of my
unpredictable query results are because I'm not using the OR rows right.
Is there some heirarchical system applied to placement of criteria in the OR
rows?
Thanks for any help