Hot answers tagged microsoft-access
NOT is a unary operator which complements its argument, eg NOT(TRUE) is equivalent to FALSE In contrast <> is a binary operator which compares two values, eg 1<>0 is equivalent to TRUE, or to NOT(1=0) This latter equivalence is the only sense in which the two are connected.
Your general application architechure (Access with Linked Tables) is probably flawed for this purpose. It can probably be fixed (mostly) but not without some revision. The key issue is, that when Access is the front end, Access itself determines whether it can submit the entire query for processing by SQLServer, and often comes to the conclusion that it ...
It will connect to whatever is in the connection string, so changing the the Source there will accomplish the goal of having it use the new Access file. The downside, is that the connection file doesn't change to match the new source and will still show the old Access file which may cause confusion later.
The first query is an A left join B. The second query is a B left join A where A.joinfield Is Null. The order of the fields in the second query is the same as in the first query. Then you put these two queries in the Union query.
Create a separate report for "All months": Duplicate the existing report. In the new report, remove the prompt and filter.
Since the prompt is coming of the criteria for the query itself, then you need to modify the query, not the report. Using Is Null and Is Not Null in a new expression you can tell Access to either use the given criteria or return all records. Copy your criteria and paste it in the top Field of a new column (Note: you do not need to include the Expr1: ...
Only top voted, non community-wiki answers of a minimum length are eligible