>>>>With my main form "A" (as top level, SCREEN=OFF in config.fpw) open, I open a new modal form "B" (desktop, in toplevel, autocenter, modal) then open a new modal form "C" from "B" (same settings as "B"). When I close C then B, the close [X] on "A" appears disabled but it still works. What could be causing this?
>>>
>>>Many of us have seen this. One trick is to issue a SHOW in activate.
>>
>>Could you expand on this? I couldn't get it to work. I assumed you meant thisform.show but that does nothing to fix it.
>
>Earlier today I noticed one of my projects - despite the fact that I thought I had changed it. I looked in activate and the code read:
>this.show
>
>I changed it to:
>=thisform.show()
>and it seemed to catch. Understand, I don't run my project forms inside the VFP SCREEN - I use a base class form as my main container form.
>
>The problem seems to occur when 2 [subsequent] modal forms are DOne (DO FORM xxx) from a MDI form control's Click. CLicking the main form's max and [then] min buttons seems to to make [X] CLose available.
>
>HTH - let me know what happens


I'm running my forms just like you are. =thisform.show() doesn't fix it for me. I have noticed that it appears to be a painting issue though. The [x] button, although it appears disabled still works. If I move a different window (any other program like Word) so that it covers the [x] partially then move it back off, the portion that was covered is repainted correctly. Cover the whole [x] and the whole thing repaints. So I issued a thisform.closable=.t. in activate... That didn't work. It must not force a repaint since closable is already .t. So then I issued thisform.closable=.f. and then thisform.closable=.t. in activate. This forces a repaint and the [x] appears enabled. However thisform.paint and thisform.draw won't fix it.
Maybe they don't affect the titlebar.