Hi Peter

I would be interested to know what you did to solve your problem perhaps it will give me some insight into how to solve my problem. For now I have add some code to minimize the form when not active and maximize it when active which forces a screen repaint and eliminates the problem when switching screens. It does not solve the problem when first opening the form.

Simon

>>Hi
>>
>>I have a toolbar with graphical check box for each MDI form open in my application. When you click on the check box it makes the associated form the active form. This gives a similar functionality as docked forms to my application.
>>
>>If the forms are maximized and you click on the Check Box in the toolbar the form is activated but controls from the previously active form are displayed in the current form. The result is a jumble of controls on the active form. This happens randomly. However if I click different Check box to activate different forms a number of times consecutively it will eventually happen.
>>
>>If the forms are not maximized the problem does not occur.
>>
>>VFP 7 documents says that the Draw method of a form repaints the form. I have tried issuing oActiveForm.Draw but it does not repaint the form. The form remains in the jumbled condition. The only way to fix the form is to change the WindowState property to 1 then change it back to 0 or 2.
>>
>>Is this some kind of VFP bug?
>>
>>I am using a Dell Optiplex PIII 450 128mb Ram with an ATI 3D Rage Pro video card and Windows 2000 SP2. I have the latest video drivers that are available.
>>
>>Simon White
>
>Simon,
>
>I don't think this is some hardware failure, but something which we all can't understand :(
>Half a year ago there was a similar thread, which I don't think was solved, though it wasn't about MDI I think.
>I myself was fighting for similar things with maximized forms (only !), and somehow this had to do with VFP not updating the resized measurements after maximized to normal again. I mean, .Width etc. was not updated until after the Resize was finished. So what to do ?
>Now 1. I can't recognize that this is your exact problem, and 2. I can't recall right now my solution to it, though it was all about maintaining myself the status about changes from normal to maximized and forth, and undertaking some additional action upon that.
>
>This was already in VFP5 and I described it as a bug. But as always : what is a bug and what do we not understand.
>If you want, I can find our solution to this tomorrow; right now I can't access our sources.
>
>0.001 eurocents; sure not more ...