>Had you succeed to execute
>

>... where .f.
>

>on SQL Server ?!
>.F. is not valid for SQL. We usually use (TableID < 0) as contidion for retreiving empty cursors. If you insist to hold your current way of giving WHERE condition you could write some expression that always evaluates to false. ForExample:
>

>... where (0=1)
>

When I executed that at first, I had the assumption it was returning all records. However, it was the previous cursor. When checking the result, I found that it was -1.

Yes, I want a condition that is not dependent on the table. The structure of each table differs so I need something generic.