Nope the value is flipping even after I have left this method. The reason I began to trace this is that the save button was becoming enabled on the primary form when it should not have been and it was becoming enabled after this subform was canceled from. .lIsOkToSave controls the save button in another method named .mToggleObjs() Secondly the sub form does not have an .lIsOkToSave property. Thirdly I dod other test that let me know

>Hi Ron,
>I haven't taken in all of the details of the replies to you, but this is my take on the prob. According to the MSDN help files:
>
>"The Show method sets a form or form set's Visible property to true (.T.) and makes the form the active object. If a form's Visible property is already set to true (.T.), the Show method makes it the active object."
>
>So pretty clearly what is happening is that your 1st 2 wait windows are referring to whatever "THISFORM" is before you create your new FORM object. Your property is set to .f. on that form. However, after the .SHOW(1) is executed, this new form becomes your active form and aparently that property defaults to .t., is that correct? If so, you will have to use a reference to your original form to continue accessing properties or methods of that original form.
>
>Hope this is somewhat helpful.