Tammy:
Putting:
Is Not Null
in the criteria row of a column in design view will mean that that the query
doesn't return that row if the column in question is Null. If you want to do
this for multiple columns then it needs to be on each column. If you don't
want the row returned where any of these are Null it has to be an OR
operation, which means putting the Is Not Null on separate lines in design
view. This could be tricky when combining these criteria with your parameter
reference to the form's control. If you don't want the row returned only
where all of these are Null it has to be an AND operation, which means
putting the Is Not Null on the same line in design view. That's less tricky
when combined with the parameter, but on the whole its easier to express this
sort of logic by writing it in SQL view. So we'd really need to see the SQL
and have a clear explanation of how you want the Nulls handled to give you
detailed advice.
Ken Sheridan
Stafford, England
Thanks for all the wonderful suggestions. I used the immediate window and I
was able to locate an error on one of my tables. I'm trying to fix that now.
I am unable to post my SQL because I am communicating via my Android phone
and I can't copy the text for some reason.
Also is there some type of code I can add to make the query ignore certain
fields when there is a null value?
Thanks,
Tammy Watts
Also try declaring the parameter, particularly if it’s a date. A date
entered in the form in a format such as 12/22/2009 might be misinterpreted as
[quoted text clipped - 17 lines]
if I don't have the forms!formname!controlname there but once I add that it
won't pull at all. Does anybody have a clue why its not pulling?
--
Message posted via AccessMonster.com
.