Jonathan,

I had this problem on a machine. Somehow, the properties on the temp folder had got inadvertently change to 'System' and FoxPro was generating the error. For some reason, Fox could not see the System folder. You'll have to uncheck the system property to fix it... I did this through the old faithful FileManager.

Hope this helps

Mace

>Have you looked to make sure there is a valid Windows temp directory and that any environment variables (like Path or Temp) that are set up are correct? These are some of the things that I want to check whenever I can get a hold of the sysadmins.
>
>Have you tried to contact someone named Mike Yates? Before I posted my original message, I did a search and found he had a very similar problem that he posted back on June 18, 1999. I tried to send him an email, but it wasn't valid. I'm not a PUTM, so I don't know if his account here is still active or not.
>
>>>>>>>We have a user that is getting an 'Invalid Path or Filename' error when trying to run our executable. We have several users, and this is the only one
>>
>>I have worked on this problem a couple of days now and have not found a solution. What I find very interesting is that a duplicate machine that another secretary uses works just fine. They are even on the same network. So I am thinking of examining the file differences on the two machines and see what directories one has that the other does not and what DLL's are present on one and not on the other. I was hoping it would be a lot simpler, but I guess there are some days where I have to earn my money. :)