>>>>
>>>>I meant that I returned value for the _screen window and used it. For some reason it worked even if OCX was part of form.
>>>
>>>Sorry, I misunderstood you. Given the other thread (in the Client/Server section) and the problems that VFP can have in dealing with certain ActiveX controls, it makes me wonder about the VB hwnd property, and how it handles it for MDI applications.
>>>
>>>Are the controls you're using for graphics? I ask because, if so, they must be using the hwnd value to retrieve a device context for the output, and if they are, then, if the _SCREEN's hwnd is used, how it's properly resolving that.
>>
>>Yes it was imaging OCX. If I remember right the necessity of Hwnd appeared when I had to build image editor (like paintbrush). It was VFP3 so I couldn't use _W.. functions.
>
>Hmm, the api must be generating the DC for the active form, regardless of the window handle (current output form). BTW, the _W.. functions have been there since at least FPW 2.6. I can't imagine that they would have left them out of the version that shipped with 3.0, but then, I've seen stranger things.

One more reason (maybe the genuine one) that I was not familiar with you that time and could not use your Foxtools insights. That application really worked with BitmapDC.