>>>>Is it a correct premise that during FoxPro's initialization the settings contained in the prevailing Config.fpw configuration file (or an aggregation of two files if 'ALLOWEXTERNAL = ON') will apply?
>>>>
>>>>Of even greater interest, can we confirm that once FoxPro has initialized, no other configuration files will have any effect, even if a subsequently called application includes its own internal Config.fpw?
>>>
>>>Yes.
>>
>>Boris, did you test that second premise?
>
>The second question (as I understand it) is "If I run VFP (instance/application) and then I run an other application built with VFP, does its CONFIG.FPW will not affect already started VFP?"
>So the answer is YES :-)
I wonder, which case will be true.
CASE 1
Config.fpw of exe1 says EXACT=ON
Results of calculations of exe1 reflect exact=on
. Included config.fpw of called exe2 says EXACT=OFF
. Results of calculations of exe2 reflect exact=off
Results of calculations of exe1 reflect exact=on
CASE 2
Config.fpw of exe1 says EXACT=ON
Results of calculations of exe1 reflect exact=on
. Included config.fpw of called exe2 says EXACT=OFF but it's not processed.
. Results of calculations of exe2 reflect exact=
ONResults of calculations of exe1 reflect exact=on
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
