>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 that is having the problem. The error appears to be coming from FoxPro, but it is before the VFP desktop has been displayed, so it is before any of our code has run. The error dialog has Cancel, Ignore and Help buttons. Cancel will cancel the application and Ignore will cause a Dr. Watson error. We have a config.fpw, and the only path stated in it is TMPFILES. The directory specified there exists.
>

IN all probability, there is a mapped drive reference that is not identical for that user and all other system users, or that user has a different set of logical drives presented. It could also be an issue with the TMPFILES assignment if it points to the root directroy of a drive that has a large number of file entries - the max files in a root directory has a fixed size that can be exceeded.

>The user has NT 4.0. The user has to get a System Administrator to install software, so his account doesn't have full Administrator rights. I don't know if this could have anything to do with it or not. I've been trying to reproduce his problem by restricting different rights to the application directory, the System32 directory, and the temp directory. I've also tried doing things like renaming the system-specified temp directory.
>

Make certain that the user's account has all necessary rights to folders that you reference on the local system - unlike Win9x, non-admin users may not have the right to access local files or folders, and this is likely the case, since if the user had admin privs, they could perform the install. Sounds like the NT Admin needs to review access rights and privileges assigned to the user account.