Thanks Chris! I'll be working on it more this evening. I'll get back to you if I need more help. I really appreciate your time.

- Mike

>You have a couple of choices. One approach is to create a config.fpw with RESOURCE=OFF and include it in your EXE when you build the app. This tells VFP not to use a resource file, so it won't create one when the app starts up. If you don't want your users to have a resource file, you can stop right there.
>
>If you do want your users to have a resource file, distribute one with the app and write it to the INSTALLDIR. You can distribute it as foxuser or as another name, like myuser. Then, in your app's startup code, do

SET RESOURCE TO myuser
>SET RESOURCE ON

(in that order).
>
>If you distribute a resource file it's best not to simply copy the one from own machine, because that one is likely to be much larger than necessary since it contains all the stored resources from your own work. Best idea is to let VFP create a new one, then make a copy of it as the name you prefer and use the copy as the one you distribute.
>
>
>
>>I knew as soon as I got excited about being done, I wouldn’t be. I put [INSTALLDIR] in the Working Directory property in the InstallShield shortcut area and everything is working great except those two pesky files (FOXUSER.DBF and FOXUSER.FPT) that are still popping up on the desktop. The shortcut on the desktop shows [INSTALLDIR] for the ‘Start In’ field. Any thoughts on what could be wrong???
>>
>>
>>>You're welcome, Mike. Enjoy those beers!
>>>
>>>>Awesome - Thanks Rick. Believe it or not, as long as I'm understanding what you're saying, that just about rapes up my upgrade (hope I'm not jumping the gun here). Once this is done, I can go have some beers. Thanks!
>>>>
>>>>- Mike