For VB, you should only have to LockWindowUpdate the parent. In VB, child controls are linked to the main forms Hwnd through internal SetParent() calls. In VFP, the VFP screens are bitmapped by the runtime engine, but message pump calls to OCX calls seem to be fed to the control (including WM_PAINT). That is probably a bug in VFP since the runtime knows the parent hwnd (which is the only native VFP control with a real hwnd) is locked, it shouldn't allow any WM_PAINT messages to child OCX controls.

You would really have to watch Spy++ messages for those controls to be sure though.

HTH,
Ed

>Ed,
>Just a question for clarification. In VFP, when using ActiveX controls, the LockScreen property of the form doesn't work. We have to use the LockWindowUpdate function as well but use the hWnd property of the control. Would this be the same in VB?
>
>>Use the LockWindowUpdate API in VB...
>>
>>Public Declare Function LockWindowUpdate Lib "user32" (ByVal hwndLock As Long) As Long
>>
>>LockWindowUpdate Me.Hwnd ' No more screen refreshes
>>..
>>..
>>LockWindowUpdate 0 ' Unlock refresh
>>
>>>I'm dynamically adding columns to a listview control inside a tab page at runtime that's displaying each column being added. Is there a way to turn off screen refreshes while the columns are being added and only refresh when all columns are added?
>>>
>>>In VFP there's a property LockScreen that I would use for this type of use.