>>I see it, and I think I know why. _SCREEN refers now to the VFP desktop. What setting AutoCenter to .T. does is center the desktop. The frame is referenced by the _VFP object. You'll note that _SCREEN.hWnd does not equal _VFP.hWnd.
>
>
>Hummm...
>
>I think there is still a little problem though. Since _VFP does not have an AutoCenter property, you can't really center the application relative to Windows by simply setting the property. Notice that if you resize the VFP IDE and issue _SCREEN.AutoCenter = .T., even the resulting positioning of the desktop is higher than expected. Depending on where the IDE is before the AutoCenter is set also seems to affect where it's moved to.
>
>Maybe I'm being picking, but Murphy's Law would lead me to believe that it could cause a problem at run-time...
>
>
>
Brian,

Yeah, if you're not aware of it. I look at it like this when it comes to applications with an MDI interface: The user is going to minimize, maximize, size, cascade, tile at their discretion. I think that if I were constantly trying to auto-center the thing, they might not like it.