Hi Daniel,

Actually, I want that both forms share the same settings. Both forms are non-modal, as far as I recall. In the main form, which is based on BaseForm class, I put this line in Init: set exact off, because I want it behave this way. The second form should also use SET EXACT OFF and not change it. If, hovewer, we add code in wgForm.Load event, which would deal with settings and I don't want to place any code in wgForm.Load, I'm in trouble...

The simplest solution, from my POV, would be provide a check via Form.Property, does this code need to be executed or not...

>Nadya:
>
>If both forms use the same datasession and they require different
>(whatever) settings, chaging the settings is not likely to be a good
>solution unless the second form is modal.
>
>If the second form is modal, you can always add a Custom object that saves
>the current settings in its Init event and restores them in its Destroy event.
>The sitaution is a little more complex if you are instantiation forms from
>classes because you may want to restore the settings as soon as the second
>form's Hide method is called.
>
>If both forms are modeless, you have to consider what will happen if the user
>switches back and forth between the forms and perform actions in no logical (to
>you) order...
>
>A possible solution may be found by examining whether it is the form or some of
>its methods that require different settings. If it's only the methods that
>require different settings, you can always follow Dragan's advice and
>save/restore settings in the methods themselves.
>
>Daniel