Christof,

EnableWindow(hWnd,1) didn't do anything obvious. Here are some more behaviors when the form comes up blank, (which isn’t every time):

1.The form instantiates not painting, the form has the image of whatever is behind it.
2.The oForm LockScreen = .F. at this point.
3.Moving the form half off the screen “wipes” that portion of the form displaying the forms backcolor.
4.Replicate(‘x’,1000) writes 1000 ‘X’es on the form.
5.Moving the form half off the screen leaves the ‘X’es intact.
6.CLEAR clears the form of everything.
7.oForm.LockScreen = .T. followed by replicate(‘x’,1000) shows nothing
8.oForm.LockScreen = .F. followed by replicate(‘x’,1000) shows 1000 ‘x’es as we would expect
9.The controls are active, meaning that data can be entered, edited and saved, mousepointer icons are active, keypress events are captured, etc.

I've captured DISPLAY MEMORY and DISPLAY STATUS to files in the Load() and Destroy() methods of forms that came up properly and blank and DIFFed the files only to see no differences except a few things like temp index names, for example, which I expect to be different.

I'm starting to believe that this is something internal that will never show on the surface, i.e., be a settable property or callable method. Thanks for thinking about this and offering suggestions.

Gary


>Hi Gary,
>
>>Spy++ seems to show that messages aren't getting through.
>
>Hmm, could the window be disabled? Could you try this code:
>

>Declare Long EnableWindow in Win32API Long, Long
>EnableWindow( oForm.Hwnd, 1 )
>