>Hi,
>A few Q.
>1. What is the influence of the setting I make in the tools->option form when I compile to a stand-alone EXE file?

Executed under the VFP runtime, none. Executed under the VFP development environment, they apply unless overridden by the CONFIG.FPW

>2. If I omit the config.fpw what settings are established?

Under the runtime, all the DEFAULT values for SET, temp files will be created in the starting directory, FOXUSER will be searched for; if found, it is opened exclusively unless flagged at the OS level as read only, if not found, it is created in the starting directory. Under the runtime, all registry entries associated with the HKEY_CURRENT_USER\Software\Microsoft\VisualFoxPro\6.0 tree are ignored, under the development executable, they are applied

>3. If the answer to Q #1 is that I get default settings without connection to the option settings, how do I know what SET commands I should include in the CONFIG that will cover all of the settings made in the developing env.?
>

You can examine the state in the runtime, but in all likelihood, the runtime deployment SET valueslike HELP, PATH, SYSMENU, etc will need to change. Also, many SET conditions are scoped to the data session, so if you use private datasessions, it'll require adding code to the Load of the Form or the BeforeOpenTables of the DE so that things like EXCLUSIVE, TALK, etc are set properly.

I'd avoid most SET items in the CONFIG.FPW; place the minimum required items such as the location of the FoxUser RESOURCE, where temp files should be, changes for MVCOUNT, etc that can only happen in the CONFIG.FPW there, and place code in the startup of the app to modify SET values; that way, if the CONFIG file is lost or corrupted, the app still will configure itself.


>Many thanks,
>
>Gadi Hutt