Over the weekend I tested some new query logic in Access 2000 and it
worked flawlessly. I get into work this morning and try it in Access
2003 and it completely deletes the WHERE criteria. Why in the world
would it behave this way? Why wouldn't it like my criteria? It is a
method for filtering on and off items that have been completed. Here
is a portion of the query:
Comp:
IIf([Forms]![FormABC]![CompFilter]=2,2,IIf(IsNull([DateCompleted]),0,-1))
Where:
[Forms]![FormABC]![CompFilter] <== this gets deleted when I open the
query.
Field "Comp" can have 3 possible results (2, 0, -1). If the form has
compfilter set to "2" then return all results. Otherwise let the form
decide which type of results to display from the query.
Something else worth mentioning is that if I have a multiple join in
other words drawing (2) lines between (2) fields in query Access 2003
does not retain that join on reEntry of the query. Everything
functions as normal while in the query but upon reopening the query the
join is gone. What's up? It seems that Access 2003 is trying to
adhere to some new standard SQL. But not giving any warning about it.
Any ideas? Any help would be appreciated.
