>Glad to hear your walk wasn't in vain
>
>Maybe the reason its traversing the path is it is looking for the support libraries?
>
>I still have no idea why Directory() would return .F. for folders maked as system.
>
>Do you?
>

No, but I have not reached that error yet in my ever expanding 'lessons learned through practical experience with VFP'.


>>
>>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'