Hi Rodney - That's my brother's name. :)

Is there anything related to your app loading at machine startup? Is there a program accessing any of the files that your program needs? Someone else mentioned blowing away the foxuser files. Actually - this may help your debugging. The foxuser files should not be part of an application. They are primarily developer tools. If this file is corrupt or anti-virus or it's attempted to be placed where security prevents, you could have a problem. So let's nip those completely. No harm should come from this, unless you are using the foxuser in your app (which I'd recommend against).

You should add the line RESOURCE=OFF to your config.fpw file. That will prevent VFP creating them at all, so they can't go bad or have user specific restrictions. :) You might also embed a config.fpw in your exe with

RESOURCE=OFF
SCREEN=OFF
ALLOWEXTERNAL=ON

You can then place a separate config.fpw with additional settings - perhaps MVCOUNT if your customer/user needs more than the default.

>Thanks for your input.
>
>What makes this so puzzling is that this is a stand-alone computer with only one user. I have seen cases where the FoxPro library is installed on a computer but only for one user and that will cause the program to fail to run when you log in as a different user.
>
>We have rebooted several times so that should clear out any instances in the background that could block the program.
>
>Thanks again for taking the time to help me with this problem.
>
>Rodney Givens