Logic in WHERE Clause

[nkimlinger]

I am customizing a third party application, using MS Access Project on SQL 7.0. I am working on a bound Access form wiht the data source of: "SELECT * FROM tableName WHERE 1 = 2". This returns a blank row, which allows the user to enter a new record into the bound table. When you remove the WHERE clause, it does not allow a new record to be entered, even with the form properties set to Allow Additions and Data Entry = Yes.

What is the logic behind the 'WHERE 1 = 2' clause? I am unfamiliar with this in a SQL statement. Can anyone explain this to me?

Thanks.

 

[SQLSister]

Sounds like the orignal programmer did this as a workaround. Where 1=2 is used when you don't want any records returned as it is an impossible condition to meet.

 

[jmj]

the 2=1 is simply pulling an empty record set.
IT helps you reuse forms. The same form can be used for a new record or to edit a record.

When you have existing data, it is pulled from the database.
Where none exists, this type of query makes an empty record set with a set of empty strings. Think of it as a way of making a new record like it's an existing record.

I use these type of records all the time with my web apps. Its saves alot of conditional logic- making the application think it's a simple edit.