>We are experiencing a variety of problems (long file open times, access errors) on a server installed VFP application. We believe source of problem is due to the fact that workstation PC's are all trying to use foxuser.dbf installed on the server, as opposed to the local foxuser.dbf that is placed on their individual PC C: drives as part of wizard install that we have been using for some time with other customers. As I'm in Maine with no access to fox/documentation (only wife's laptop), I'm in need of assistance. Can someone tell me what determines which Foxuser.dbf is used by an application... and offer any suggestions as to how to point PC's to the local PC's foxuser.dbf as opposed to the one on the server?

Whoops, hit send too early. If no configuration file is found, the default is the current directory (application directory). If the resource file isn't important to your application, just sticking a config.fpw file with RESOURCE=OFF in the application directory should solve the problem.