>>Hi Henry,
>>
>>In the main application main program we issue couple of SETs commands, and, BTW, the default state for our system is SET EXACT ON (which I personally don't like much, especially because the system currently doesn't care about restoring settings after it finishes, so I have to issue SET EXACT OFF in command window). The same number of set's commands are repeated in BaseForm.Load event. We have another form class called wgForm. This is a replica of VFP Base Form class with only two properties set (ShowToolTip and DS set to private). Recently my colleague added the same code in Load as we have in BaseForm.Load, but I immediatelly found a case, where this would cause problems, so my colleague will revert these changes back to its original state (no code).
>>
>> As a simple solution here would be a logical form property, which tells us, do we need to change settings or not...
>
>You could also consider creating a privatesessionsets class. This class would have properties for all the private settings. You can drop it on your form class however, don't drop it on the child form class.
>
>Or, you could as you said, do something like...
>
>If ThisForm.DataSession = 2
>
> ThisForm.AddObject('privatesets','privatesessionsets')
>
>EndIf
>*************
>BOb

Thanks, Bob. Actually, I feel everyone suggestes something more complicated, that it has to be.

Thanks to everyone. The current problem solved by just reverting to none code at all, but I will grab all the ideas, and we'll see, that can be done...