read only tables

We are having problems where client machines cannot update tables.
We are using vfp6 and the data is on a 2000server.
The client machines are 2000 pro.

When trying to write to a table we occasionally get error 111 'cannot update
the cursor'.

According to the help this is because the table is read only.

This has happened with two different tables now and there seems to be no
pattern to it.

The error persists until the server is restarted. Until then the table
cannot be written to.

How can a table suddenly become read only?

Has anyone else experienced this problem.

Any help would be appreciated

Dave

Leemi
Thu Sep 16 08:30:49 CDT 2004

Hi Dave:

Are you running VFP 6.0 in a Terminal Services environment?

Are you running anti virus on the workstations or the server? If so, I
would configure the anti virus so it does not scan the VFP data files or
temp files. Here is an article showing how to do this in Norton:

321550 How To Optimize Visual FoxPro Applications While Using Norton
AntiVirus
http://support.microsoft.com/?id=321550

Finally, are you running any backup software? If so, disable it for
testing purposes. Sometimes backup processes can lock a file that it is
trying to back up.

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP9 Public Beta Now Available!! --*
Download the VFP9 beta here: http://msdn.microsoft.com/vfoxpro/

*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003

>We are having problems where client machines cannot update tables.
>We are using vfp6 and the data is on a 2000server.
>The client machines are 2000 pro.

>When trying to write to a table we occasionally get error 111 'cannot
update
>the cursor'.

>According to the help this is because the table is read only.

>This has happened with two different tables now and there seems to be no
>pattern to it.

>The error persists until the server is restarted. Until then the table
>cannot be written to.

>How can a table suddenly become read only?

>Has anyone else experienced this problem.

>Any help would be appreciated

>Dave

dave>
Thu Sep 16 11:47:02 CDT 2004

We are not using terminal services but they have norton antivirus installed
with realtime scanning disabled.
Thanks
Dave
"Lee Mitchell" <Leemi@online.microsoft.com> wrote in message
news:4R3R2F$mEHA.2100@cpmsftngxa06.phx.gbl...
> Hi Dave:
>
> Are you running VFP 6.0 in a Terminal Services environment?
>
> Are you running anti virus on the workstations or the server? If so, I
> would configure the anti virus so it does not scan the VFP data files or
> temp files. Here is an article showing how to do this in Norton:
>
> 321550 How To Optimize Visual FoxPro Applications While Using Norton
> AntiVirus
> http://support.microsoft.com/?id=321550
>
> Finally, are you running any backup software? If so, disable it for
> testing purposes. Sometimes backup processes can lock a file that it is
> trying to back up.
>
> I hope this helps.
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> Sincerely,
> Microsoft FoxPro Technical Support
> Lee Mitchell
>
> *-- VFP9 Public Beta Now Available!! --*
> Download the VFP9 beta here: http://msdn.microsoft.com/vfoxpro/
>
> *-- VFP8 HAS ARRIVED!! --*
> Read about all the new features of VFP8 here:
> http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
> Purchase VFP8 here:
> http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518
>
> Keep an eye on the product lifecycle for Visual FoxPro here:
> http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
> - VFP5 Mainstream Support retired June 30th, 2003
> - VFP6 Mainstream Support retired Sept. 30th, 2003
>
> >We are having problems where client machines cannot update tables.
> >We are using vfp6 and the data is on a 2000server.
> >The client machines are 2000 pro.
>
> >When trying to write to a table we occasionally get error 111 'cannot
> update
> >the cursor'.
>
> >According to the help this is because the table is read only.
>
> >This has happened with two different tables now and there seems to be no
> >pattern to it.
>
> >The error persists until the server is restarted. Until then the table
> >cannot be written to.
>
> >How can a table suddenly become read only?
>
> >Has anyone else experienced this problem.
>
> >Any help would be appreciated
>
> >Dave
>

Jan
Fri Sep 17 09:33:19 CDT 2004

Dave,

Check the event log on the server and see what errors are occuring. You may
have buggy NIC drivers or a network problem.

Rgds
Jan

<dave> wrote in message news:414963fa$0$5454$afc38c87@news.easynet.co.uk...
> We are having problems where client machines cannot update tables.
> We are using vfp6 and the data is on a 2000server.
> The client machines are 2000 pro.
>
> When trying to write to a table we occasionally get error 111 'cannot
> update
> the cursor'.
>
> According to the help this is because the table is read only.
>
> This has happened with two different tables now and there seems to be no
> pattern to it.
>
> The error persists until the server is restarted. Until then the table
> cannot be written to.
>
> How can a table suddenly become read only?
>
> Has anyone else experienced this problem.
>
> Any help would be appreciated
>
> Dave
>
>