It seems that ExecuteSQL in the following case:
"WHERE Inactive <> 1"
does not work when the number field "Active" is empty. In other words "Inactive <>1" is evaluated as "False" if "Inactive" is empty.
If Inactive has been set to 0 (zero), the above WHERE clause evaluates correctly. So the workaround is to simply use a AutoEnter calc to set the field to 0 (zero) whenever it is empty.
Is this known and expected behavior?
Thanks for any insights ...