Also check for accidental trailing semi-colons (;) on any SET PATH commands (or similar where a path name is at the end of a line) - it will include the next line of code in the path and give you this error.

I found this out the hard way - in my case everything ran fine using VFP or a single EXE run-time but if I ran multi-user *some* machines would report the error.