Yes, I always use unique keys in my projects, but this one is not our own project...

Thanks for the solution, it works.


>Christian,
>
>First of all, all I can say is "Wow, you really need a unique key!"
>
>But, you I suppose you could add the record number to the view, and do it the way you did it in the past:
>
>

>select recno() as nRecno, ... and so on

>
>>Hello,
>>I'm stumbling about a normally simple task:
>>
>>I have a view that is a subquery of a large table.
>>If the user changes a record in this view, I need to check in the large table whether certain values that have been are still unique.
>>
>>In former times (without using a view) I just opened the table again and compared RECNO() of both tables, so if they were the same it's the same record.
>>
>>The table does not have a unique key (badly enough, but inherited from long ago), so I cannot really find out whether the edited record in the view is the same record in the table, if I found a "double" entry.
>>
>>Is there a way to check on the identity of the record without using RECNO() or another unique key?