13. ledna 2012 23:55
Hoping the VFP group can help me with this because I'm getting nowhere with Novell Of course they always blame Microsoft when they can't solve a problem. . .
I have a small Netware 5.1 network, some users running XP, some running Windows 7 with the newest release client. Running Visual Foxpro 6 or 9, same problem.
Periodically, we get a Visual Foxpro error that the table is read only. The user in question has fully supervisory rights to the file and directory, so its not a rights issue. I checked the Windows 7 security tab - user has full security access, rights, etc.
The exact error message is: "The record is read-only". When the user types an escape, the error comes up: "Cannot update the cursor".
This is extremely frustrating because it is intermittent and we cannot find out what is causing it. The program code works just fine on Windows XP, so it seems like its a Windows 7 problem. We just cannot isolate it.
Is there something that I need to configure or change?
Thanks for your help.
14. ledna 2012 21:27
This is, what you describe, a know fact of Windows7. Most probably you have installed your application somewhere in C:\Program Files x86 - which worked perfectly in pre WindowsVista, howeve MS has decided this is no good anymore. You should change.
A full story of why/how is published by Rick Schlummer : http://rickschummer.com/blog2/2010/11/windows-7-gotcha-with-visual-foxpro-apps/ and more articles can be found on the internet on this subject.
16. ledna 2012 16:34
Thanks, I checked the article and the comments. My Foxpro application is installed in c:, by Foxpro programs are installed on the Novell Network at f:\apps\foxprow\programs, and all data files are on the Novell Network in f:\data\dbase. So, unless I am missing something, this should not be a problem, or is there some configuration tab I need to "tick".
- Upravený ostrowlaw 16. ledna 2012 16:43
16. ledna 2012 17:06
Novell & Win7 & Foxpro seemed to be an issue as well. Once switched over to Windows Server, no issues. Is the problem always on the same screen? Could be your code too.
18. ledna 2012 19:23
Well, I went back at looked at the program - perhaps it was a misplaced rlock() or flock() here or there. They were OK, tightened it up -- works find under Windows XP.
I then saw some posts about possible virus scan program problems so I removed MS Windows Defender (having previously excepted the f:\data\dbase directory) and installed a different virus program (AVG). Better, but still getting the errors. Received a cursor read only error this morning.
I am convinced it is a Windows 7 problem, or else a Novell client problem, but there must be something I can do short of resorting back to XP (a very short term solution) or changing file servers (rather extreme). . . .
- Označen jako odpověď Mike FengMicrosoft Contingent Staff, Moderator 29. ledna 2012 7:10
1. srpna 2012 19:33This is definitely a problem caused by Windows Defender. I installed an update, which in turn wiped out all necessary files for our software running Foxpro. I have disabled Windows Defender and reversed installing the update. It's now working perfectly! I've also changed my updates to notify me instead of going through auto installs so that I can track them.
14. srpna 2012 17:13
Actually, I solved my problem in a different way because my problem was caused by Novell's client. I changed the file caching to "off" in the Netware client and it was resolved.
If you are running a Novell network I would definitely change that setting.