>Terry,
>
>We do use the modeless MDI forms, but allow the user to turn the MDI off with a preference setting. There are some annoying side effects to the MDI forms. Namely, when you maxamize one, they all maxamize, and when you restore one, they all restore. I'm not sure who decided on that little bit of standardization, but they missed the boat in my opinion.

It sounds like they share the same sub-class. Look at the resize event - maybe a DEFAULT direction is needed.

>
>Speaking of the Close box,
>We have found that no matter what you do, when the report designer, or print preview is open, the close box for the main application screen is always enabled. We would like it disabled when either of these are open.
>
>Tried:
>Setting _screen.closable to .f. just before modifying/previewing as well as putting _screen.closable in the load,init,active,show events of the form the modify/preview are shown in. Nothing worked.
>
>As a workarround, we have created an ON SHUTDOWN routine that just returns when the user attempts to close the main application screen when either of these is open. We call this just before the report command and reset it right after, or in the error routine if needed.
>
>Don't get me wrong, we love VFP. There just a few remaining annoying quirks. Hope some of them are fixed in 9.

I know what you mean. But, just when I thought I would have to scrap some significant pieces of the job, it all started to work. I know it's a pain - it's a very eloquent paradigm. When it works as expected - it all seems worth it.

>
>Jim McConnell
>
>
>
>>I found that using modeless (MDI) forms [seems to] clear up the close button issue. In some cases, you can re-activate the close button by clicknng the form's icon.
>>>Simon,
>>>
>>>Yes, very annoying. I see it in our compiled apps/exes as well. Customers hate it..... It's not just the close button.......
>>>
>>>Another thing I find annoying is the way the Project Manager v scrolling jumps. It's almost like using the v scroll bar does not set the focus back to the project manager like it should. Seems like it only does it once in a while, but usually when I already frustrated with something.
>>>
>>>Jim McConnell
>>>
>>>
>>>
>>>>Hi
>>>>
>>>>Has anyone else noticed that VFP8 SP1 does not always recognize a mouse click.? For example I can sometimes click on a button in my application and nothing happens forcing me to click it again for the button to work. I have never seen this in any other version of VFP but I see it quite often in VFP8.
>>>>
>>>>Another annoying form of this problem is that I can often click on the Class property sheet and start typing only to realize the property sheet does not have focus desipte the fact I clicked on it. So I have to click a 2nd time and re-type the property value.
>>>>
>>>>I am running WinXP SP1 with 500mb ram and VFP8 SP1.
>>>>
>>>>Thanks
>>>>Simon White