<>False

[alex]

Hello Experts,

I have a query in Access that contains several AND/OR statements. When
I view the query in SQL or Design mode, Access adds <>False to the end
of each SQL statement or in the criteria section (design mode).

Can anyone tell me the purpose behind this logic? Thanks for any help.

E.G.,

WHERE (((TBLO.XNUMBER) Is Null) AND ((TBLO.TR_DATE)<=(Date()+120) Or
(TBLO.TR_DATE) Is Null) AND ((([TBLO].[OTHER_INFO1]) Not Like '*CODE*'
And ([TBLO].[OTHER_INFO1]) Not Like '*ARC*' Or ([TBLO].[OTHER_INFO1])
Is Null)<>False) AND ((([TBLO].[OTHER_INFO2]) Not Like '*CODE*' And
([TBLO].[OTHER_INFO2]) Not Like '*ARC*' Or ([TBLO].[OTHER_INFO2]) Is
Null)<>False) AND ((([TBLO].[OTHER_INFO3]) Not Like '*CODE*' And
([TBLO].[OTHER_INFO3]) Not Like '*ARC*' Or ([TBLO].[OTHER_INFO3]) Is
Null)<>False) AND ((([TBLO].[OTHER_INFO4]) Not Like '*CODE*' And
([TBLO].[OTHER_INFO4]) Not Like '*ARC*' Or ([TBLO].[OTHER_INFO4]) Is
Null)<>False) AND ((([TBLO].[OTHER_INFO5]) Not Like '*CODE*' And
([TBLO].[OTHER_INFO5]) Not Like '*ARC*' Or ([TBLO].[OTHER_INFO5]) Is
Null)<>False))

 

[Allen Browne]

Access has to show something in design view.

If you create a complex expression that evaluates to True of False, the
expression is shown in the Field row, and Access indicates that the
expression will be evaluated as True by displaying <> False in the Criteria
under the expression.

While this convolution is necessary for the display in design view, it
certainly doesn't improve the meaning or readability or efficiency of the
SQL statement.