Barbara,

Yes, you're right. Sorry for the lack of clarity on my part. When the message box and/or browse window is closed and I return to the main form, which is at that point the only active window, the close button is disabled. Since yesterday I found that if I suspend the program and then set sysmenu to default, then my close button will be active again, which is similar behavior to choosing one of my form's command buttons to run a report to screen. The problem is that programmatically I cannot do anything to simulate this behavior, including setting sysmenu to default. Any ideas?

Thanks,
David

>David,
>If you have a message box or other modal form open then you must close it before your other forms will become active. This is the correct behavior for modal forms (and the message box is simply a pre-designed modal form).
>
>HTH
>Barbara
>
>>If I run a message box or browse window under my current form, then the close button ('X' in top right corner -- the internal Windows thing) becomes disabled! How come? If I do not run these, all is fine. For example, I can run another form, or run a report preview, and when I return to the parent form the close button is still active.
>>
>>I have tried forcing the .Closable property to be True in the "on activate" method of my form, but it makes no difference.
>>
>>Thanks!