>>>>The thing is I am getting this error also, on a machine using Win 98. Is system a property used in Win 98 directory structure?
>>>
>>>Yeah it is. It is a RO property on the folder in explorer. I bet you if you try the directory() func on such a directory it will incorrectly return .F., and even worse, mkdir will error.
>>>
>>>You can set or remove the attribute using the attribute in dos. It must be .T..
>>>
>>>Probably you temp directory has this setting.
>>>
>>>Mace
>>
>>Well Mace I will walk over to the other building and check this out. I need the exersize and I am intrigued if this is the answer.
>>
>>I will post back here shortly.
>
>Let me know

I finally found the answer. It was not in the RO or System permission. But Mace you got me thinking about the path. So I decided to open the DOS window on their machine and do a PATH command. I wanted to see if any of the path was in the RO or SYSTEM condition, but what I saw was that someone had added to the path in the autoexec.bat file and forgot to separate one path from another with a semi-colon (;). Thus when ever foxpro fired off my exe the path was being checked and the error 'Invalid Path or FileName' was being displayed.

So that was the answer to that installation problem.

Now the real question I have for any VFP knowledgeable person is why is FoxPro traversing through the path when my exe is fired? The START/PROGRAMS/NSWC VFP APPLICATION defines where the exe is and the start in directory. And the config.fpw file is located in the defines start in directory. So why is the DOS path being traversed? If I cant stop it from being traversed then how can I stop this error from happening in the future, as I know the autoexec.bat is out of my control on all the machines that use my app.

Oh by the way I did ask who changed the autoexec.bat file and got the answer I figured, 'I don't Know'