Leemi
Mon Dec 29 10:01:51 CST 2003
Hi David:
The first thing I would do is try to determine what file(s) are causing the
error. This might help use diagnose the cause. Go to www.sysinternals.com
and download Filemon. Run this on the machine that throws the error and
examine the log after receiving an error. This should tell us what file is
causing the error.
Other suggestions to try:
1. Disable any anti virus software or at least prevent it from scanning VFP
data file. See this article for an example of configuring Norton AV in
this manner: 321550 HOWTO: Optimize Visual FoxPro Applications While Using
Norton AntiVirus
http://support.microsoft.com/?id=321550
2. Make sure all the operating systems have the most recent Service Packs
installed.
3. Make sure that all versions of VFP have the most recent Service Packs
installed. If you are running custom EXE, make sure the runtime file
(VFP6r.dll, VFP6renu.dll and VFP7r.dll and VFP7renu.dll) are the same
version as that used to compile the executables.
4. Make sure all your VFP temp files are going to unique folders for each
user and that the AV program is not scanning them files or folder.
I hope this helps and have a Happy New Year.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell
*-- 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 retires Sept. 30th, 2003
>I have a problem that someone out there may be able to
>help me with. We have a network with a server running
>Windows 2000 Server. There are several workstations on the
>network running different operating systems namely Windows
98 and Windows XP. The server primarily stays on
>continuously. Workstations are generally shut down each
>evening. On each of these systems there are two distinct
>programs accessing the same database's tables and indexes.
>One program is complied with Visual FoxPro 6.0 and the
>other is compiled with Visual FoxPro 7.0. For the most
>part this seems okay but we occasionally get an error
>message "1705 File access denied". We get this message at
>time when only one user is on the system with only one of
>the programs open after other users have been into and out
>of these programs. We suspect having the programs compiled
>under two different versions of FoxPro may be at the root
>of this. To get both programs compiled under the same
>version of FoxPro in this instance sounds easier than it
>will actually be. We're willing to do this if we had some
>good indication that this would solve the problem and it
>isn't something else say operation system related or say
>accessing the files with other programs namely Excel.
>Thank you in advance