>I have a VFP 6.0 application that is distributed thru the internet, and for some users, this application will place the Foxuser.dbf and Foxuser.fpt on their desktop.
>
>This application is installed using Visual Studio Installer, and the problem occurs when the executable is started. You can delete the files after quitting out of the application, but they will return when the executable is started back up again. As far as I know, this happens on both Windows 95 and Windows 98 machines.
>
>The application has a foxuser.dbf and foxuser.fpt file located in the data directory of the system (WCCalc\Data\Foxuser.dbf). There is a path statement in the startup procedure that has the Data directory included, so the app should find these files when it starts.
>
>Since this only happens on a very few machines, and I can't reproduce it, I'm kind of baffled on what could be causing it, and how to fix it. The only thing I can think of is that Visual Studio Installer somehow will either put something in the registry or somewhere else that does this. I do have Visual Studio Installer put a shortcut on the desktop of the executable, but the problem occurs for both the desktop shortcut and the shortcut located in the Start/Programs area. This shortcut on the the desktop is the only reference that I know of to Windows desktop. The system doesn't have any connection to that at all.
>

If the CONFIG.FPW doesn't specify a location, and there is no FOXUSER file in the Starts In directory (in all probability, the shortcut doesn't have one specified) and RESOURCE = OFF isn't specified, VFP will make new FOXUSER files in the Starts In directory - putting the direction in executable code is too late, since the decision has already been made. Either put a RESOURCE=OFF in CONFIG.FPW and set it in code, or specify a Starts In directory in the shortcut to avoid this problem. I'd suggest RESOURCE=OFF, and then let your code direct to the right place once the app starts.