Hi Henry,

It is hard for me to understand, why do you experience this weird behavior. Basically, as long as you use private DS all temporary cursors and tables opened during form's life time, would be closed automatically, so you don't have program CLOSE TABLES. Setting combobox rowsource to nothing would not hurt, though not really needed. Why the new button works and the old one doesn't is a mystery. I can speculate, that the difference is in the order of the objects destroyed (old button is destroyed first), but it is just a WAG. If you would be able to reproduce this problem on the simple form, it may help. Otherwise I would probably leave the problem behind as "unsolved mystery" as long as workaround exists.

>>>2. Why does this happen only when Page 4 is access by the user?
>>Is combobox on the 4th page? Or the form itself?
>>
>The combobox is on the form. The InterActivechange executes select statements to populate grids and other controls in the pageframe. Page4 has the basegrid.
>
>>>3. Why isn't the cmdReturn button which is part of my baseform releasing the form (actually does nothing).
>>
>>After the error in Destroy method it doesn't correctly work and release this form.
>
>But, this does not happen with the 2nd cmdReturn I placed on the form.
>
>Thanks Nadya.