Even better. As far as I understand, VFP windows and controls are now REAL windows! Until now, VFP forms and controls where a strange kludge using bmps.

To be able to adapt VFP to W2K standards on accesibility, a good deal of the video display has to be rewrote.

Indeed, that opens up a host of new possibilities and eliminates many shortcomings. I hope for example, that this favours VFP performance over Terminal Services, and also solves the many refresh problems with some ActiveX controls.

There is some MS people that could confirm my beliefs?

Thanks in advance!



>>>Forgive me for asking stupid questions, but what can you do with that hWnd handle?
>>
>>You can use it for any Win32 API function that requires a window handle. As an example, GetWindowText() would require a window handle. Check the MSDN for "Window Functions" under the Platform SDK treeview node.
>
>One thing that immediately comes to mind would be to use LockWindowUpdate() to keep an ActiveX control from updating. Assuming that the control doesn't expose a window handle property or function, having the form's window handle easily accessible gives you a good starting for FindWindowEx() to locate the control's.