>>I was just wondering what everyone is dropping into their CONFIG.FPW files now a days. I am using the following:
>>TITLE=My App Title
>>SYSMENU=OFF
>>SCREEN=OFF
>>TMPFILES=C:\TEMP\
>
>For multilingual applications, there won't be a TITLE because it has to be generated at run time.
>
>SYSMENU=OFF has probably been removed by SCREEN=OFF and _screen.Visible=.T. after the setup.
>
>In my case, I only have RESOURCE=OFF and SCREEN=OFF. I try to make the most of the configuration in the setup but those two need to be in CONFIG.FPW.
>
>>This seems to do the trick for me. Also, do we still need CONFIG.FPW for VFP 5.0? Any additions or comments welcome...
>
>No, you don't need a CONFIG.FPW. However, if you don't have the minimum RESOURCE=OFF in CONFIG.FPW, this mean the EXE will try to create FOXUSER file for the user, and in a network environment, they might not have the rights to create it. Also, in an EXE, most are using RESOURCE=OFF to avoid the FOXUSER file. As for saving the window coordinates and other things, we mostly use INI files or register entries. Avoiding FOXUSER file will also speed up the system a little bit.

Thanks for the tip!, RESOURCE=OFF, I am always looking for ways to speed up those darn apps. So, you don't worry aoubt the old Foxpro temporary files anymore? I remember a SORTFILES or something also from my FPD days. Are any of these useful anymore?