>Hi
>
>My application is in use by 10 machines all over the UK.
>
>Each installation is stand alone.
>
>One of my users is having problems where a table seems to be being opened as READONLY?
>
>This seems to be intermittent, this problem is not occurring to my knowledge on any of the other 9 installations.
>
>I open my tables using the dataenviroment of each form.
>
>It is always the same file that this is happening on.
>
>The error I get when trying to update this file is obviously "Cannot update the cursor SCHEDULEBODY, since it is read-only."
>
>I have used GOFISH4 and can find no other ways this file can be being opened READONLY? dataenviroment for this table is set to Readonly .f.
>
>1) Anybody got any suggestions on how this could be happening
>
>2) Using the ISREADONLY command I am quite willing to write a routine that
>checks a passed tablename is open as READWRITE and if not will open it in the same select area as READWRITE with same indexes/order set.
>
>3) Or should I be capturing the error and trying to reopen the table as READWRITE as part of a n error trap routine?
>
>Any help much appreciated

I have a client who gets this error occasionally. I asked about it here in thread #1599929. My best guess is that it's somehow related to opportunistic locking.

Tamar