Benoit ---

I don't know to what degree the Clipper engine would support SQL passthrough commands within ODBC, but it would seem to me some sort of LOCK() via SQLEXEC might be needed. Like Colin said, locking the view is useless.

>
>I'm not sure how you would lock the physical record in the clipper table but when using views, both local and remote, the view is local to each user so the record lock is not needed. You might want to look into the CURVAL() OLDVAL() functions to handle more than one user writing to a record in the clipper table.
>
>>I have to work with clipper table use by a clipper application an I c'ant modify the clipper app.
>>
>>I use Intersolv odbc driver for accesing the table an update the index
>>
>>I creat a remote view to work with the clipper table. I want to lock a record in the view an lock the same record in the clipper table at the same time.
>>
>>It work in the view but when I use the clipper application to work with the table the record not lock.
>>
>>Is the Remote view a good way to use odbc.
>>
>>
>>Any tips will be appreciate
>>
>>Thanks
>>Benoit from Québec