Ashley,

>As mentioned below, yes and the resource is set to OFF
The question was because it was not clear to me if you mean the loader exe or the loaded exe.

Remains the question of version of VFP?
Do you set resource on somewhere in your programm?

Can you use a development version on the machines with the problem?
Check Registry key HKEY_CURRENT_USER\Software\Microsoft\VisualFoxPro\8.0\Options. (7.0 respective) VFP Seting are stored there.

For using -C switch. There are some odds with it. See Thread #866291

Agnes

Update:
You have config.fpw included in your loader?
>
>
>>Hi Ashley,
>>
>>do application called by the loader have a config.fpw included? If Yes, what are the settings for RESOURCE? Which version of VFP do you use?
>>
>>
>>Just for couriosity (I'm working on my own loader) do you call with RUN/! or with ShellEcecute?
>>
>>Agnes
>>>I am having an inconsistent problem on a small percentage of workstations..
>>>
>>>My app is called by another small VFP "loader" app.
>>>This loader EXE resides on a Novell network drive visible to the users.
>>>The config.fpw is compiled into the exe and specifies a local dir for TMPFILES and RESOURCE = OFF.
>>>
>>>On some workstations it tries to create/write the FOXUSER.DBF to this common Network drive, which the users have read-only access and results in an error.
>>>It also seems to ignore the TMPFILES setting and attempts to create VFP's temporary files to this drive.
>>>In some cases, the drive is another network drive which is read-only too.
>>>
>>>The only clue I have is that some of these PCs did use another FoxPro application in the past, and my app seems to be picking up on this and attempting to use the "Invalid Resource file".
>>>I have tried adding the -c switch and pointing it to a copy of the CONFIG.FPW file I use - no effect.
>>>
>>>As I said above, this problem only affects about 1 in 15 users..
>>>
>>>Any ideas, anyone?
>>>
>>>TIA