I have a VFP6 application (running as an .exe) which retrieves and writes-back data to a SQL7 back-end using remote views. When users are in the application and a particular view is open (based on one table only - no joins), I cannot do any manual modifications to the corresponding back-end table (not necessary the same records that users are looking at). It is if some sort of lock is in place. When all users quit the application, the 'lock' is released and I can modify the data table directly.

This problem only occurs with one table. I have checked permissions on this table and they are no different from any other table which is behaving 'properly', ie. I can change data to the back-end while other users are using views based on the table.

All records are optimistically locked. SET EXCLUSIVE is definitely OFF in the application (although I don't think that has anything to do with it as all views are stored as local cursors, aren't they?)

Does anyone have any ideas why this behaviour is occurring? I was under the impression that when a view has been loaded from the back end, the two tables (view and back-end) were totally independent until a TABLEUPDATE or TABLEREVERT was issued.

Any help would be appreciated.

Alan