Thanks - I think I visited the CONFIG.FPW issue in `98 regarding MVCOUNT. So easy to forget - and so difficult to re-instate.
>> I noticed today that it seems CONFIG.FPW has no affect unless the EXE >> (as opposed to a PRG) is running. > >Yes, I think a good rule of thumb would be that CONFIG.FPW will be honoured if and only if a new instance of the Fox runtime is being started. > >So, if an .EXE is started from the operating system level then the config will be used, but if you DO the same .EXE from an already-running Fox then the config will be ignored. Similar things apply to Fox .DLLs, where a bound config will be used when the first instance of a class from that .DLL is created (because this causes the .DLL to be loaded which in turn loads a copy of the runtime). > >I think this makes sense if one looks at CONFIG.FPW as a means of configuring and initializing the Fox runtime, rather than as a means of specifying the initial state (and optional initial command) of an application.
