>>>Sorry to disagree, but for a simple single table select in which you want to verify that you are picking up the correct records (and primary keys aren't always an option)there is no problem using recno(). Sometimes you've just got to get the job done - the context makes the difference.
>>
>>Where can yo not get the primary key from? I do views instead of working with tables directly. Without a PK, I could never get my updated data back to the table.
>>
>>In the view designer or any of the dbsetprop() commands recno() is not an option.
>>
>>__Stephen
>
>_Stephen
>
>As I stated, the context makes all of the difference. You are thinking of the use of recno() in a select statement solely in the context of an application.
>
>Not all data originates within our data entry interfaces where a primary key would have been enforced. If a client provides a file of external data and needs a specific portion of it the use of recno() in a select statement may be appropriate when manipulating that data from the command line.
>

Nope.


>I cannot tell from Wai’s question why he needs this answer, can you?