Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
File Access is Denied ??
Message
From
23/01/1997 23:55:27
Bill Gravell
Indoor Purification System
Menifee, California, United States
 
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00018217
Message ID:
00018298
Views:
43
>>>I am getting a "File Access is Denied" error during a runtime exe application. The system is on a network, and I don't have any files that are write protected. I can't reporduce the problem in the development version, and I can't envoke the debugger from the exe.
>>>
>>>Anybody have an idea of how to go about finding the culprit?
>>
>>By chance are U running a Novell network and logging into your system as a user who may not have rights to that directory. Make sure all of the proper network rights are assigned to the user/user groups necessary. I had similar problems on a pathworks network. All users had the exact same access rights except one... I think one of those create things or something. That is where I would start.
>>
>>Next try to reproduce the problem in a development environment where U can use Trace & debug. Put wait windows into your code to assist in narrowing down where the code is hitting a road block; provided U do not have a robust error handler. Can U access the data files from the command window? Well just some quick thoughts.... Steve
>
>And most obvious: Check for exclusive use of files. This is a common problem when porting a stand-alone application to the network for multi-user access.

Thanks Steve....I found it this afternoon. Seems as though VFP doesn't really care for arrays or tables named "Temp". The original author of this system used temp everywhere. In one spot he used a select statement to create a table called temp, and when 2 users went into that section of the system, the 2nd user couldn't access the temp.dbf that was inuse from the other users sql select. I changed the name and made it a cursor, and the problem went away. I found it by looking at "Netwatch" and saw the file being used by one user and not by the other. then the name struck a bell, and the whole situation became clear.
Previous
Reply
Map
View

Click here to load this message in the networking platform