Nope that's not it. I use relative paths everywhere. For example, in the set path I use:

SET PATH TO (JUSTPATH(JUSTPATH(_VFP.Servername)) +";" + addbs(justpath(_vfp.ServerName)) +"Plugins"

This gives me the path to the Main.exe and the plugins folder which is what is being executed at this point. However, I did some small changes after my post and I think it may actually be a SET HELP TO command that is interfering and giving the error.

I have:

SET HELP TO

in a procedure that I call for settings. I'm beginning to think this is causing the "File not found" error. Especially when you consider that the File Not found error takes a parameter and here it is empty. I will try SET HELP OFF tommorrow and see what gives. The other reason I'm thinking that it's this is that on my dev PC the program reverts back to Fox's help file whereas that file is not available on the second PC.

Thanks though

Richard




>Do you have a SET PATH TO setting in the app? Does it include the Plugins directory? If so, are you referencing the Plugins directory as a relative path or an absolute path? You should be setting a path to Plugins as a relative path.
>
>
>>First the background:
>>
>>I have a main program that uses dynamic linking to classes contained in executable files (plug-ins) contained in subfolders. So that my folder tree looks like this:
>>
>>Main Folder
>> Plugins
>>
>>The main program has no problem linking to these plugins. I used the NewObject() method to create visual class (in this case it's just a container.) No problems.
>>
>>Now, I'm trying to do some automation using Windows Scheduler. I use SET PROCEDURE TO "..\Main.exe" in the plugin to get to some common Procedures contained in that. This is the line the error occurs on. I have a second machine that has Windows XP SP2 set up on it. Since the machine is not logged in, there are no drive mappings and I have to use UNCs to run the application. Now when I run the plugin for automation, I get a "File not found" error. If I click ok, the plugin will continue as planned, except for this error. Here's the catch, I don't get the error on my development PC at all. The only difference between the two is I have foxpro and VS.Net 2002 installed on the dev PC.
>>
>>What I've tried:
>>TRY...ENDTRY (FAILED) Message still comes up.
>>ON ERROR... (FAILED) Messsage still comes up.
>>
>>My Question:
>>Why am I getting this on one machine and not the other? Is there something I'm missing?
>>
>>Thanks
>>
>>Richard