I found it by myself
It should be
1 ≠ 1
1 ≠ 2
Dont know why buth the double ≠ operator is causing the problem.
Did not solved it.
What you post in your last comment does not match the SQL examples in your first post. There are a number of reason why comparing the value of a field to the results of ExecuteSQL might fail--in particular, the query might be returning values from multiple records.
But I think your last expression can be changed to:
Field 1 ≠ 1 AND Field 1 ≠ 2
Field 1 ≠ 1 or Field 1 ≠ 2
will always be true as any value that you select for Field 1 will always cause the expression on one side or the other of the OR operator to be True.