>>Where did you find documentation for the functions that begin with an underscore? They're not in the help file. Didn't you just "hack" them. That's what I did with some of the others before I got my hands on the documentation.
>
>They're in my help file... They're part of the LCK API and have also been exposed
>in FoxTools. Not all _ functions are there but many are...
>
>>Vlad's got a point, but I'm there should be a way around it.
>
>Why would you ever have two windows with the same name??? If you do multi-instanced
>forms the titles should contain some unique information that relates to the form.
>There's another function (the name of which escapes me) that you can use to pass
>an actual window reference to (It has to the active window). You can then use
>that function instead of Wfindwindow...
>
>I'm just really trying to stay from ActiveX controls whenever I can because of
>the update issues. I have enough headaches trying to keep my Treeviews in
>synch with the DLLs out there :-}
>
>+++ Rick ---

I thought that the LCK was included with the professional editional of 5.0. I've got basically the same stuff (make, c, c++, include files) I've had in the 2.6 LCK, but no help file. Maybe it's on the CD. I'll have to look.

You do have a point about forms with the same name. You could use the name clause in DO FORM..., or modify the caption to indicate the second instance of the form before the .Show if you used CREATEOBJECT().

As far as ActiveX, I think that you've got to take the good with the bad. Use what you have to and forget the rest. Certainly, FoxHWnd does have its own idiosyncracies. However, if you can deal with it, I believe that it does have some advantages. What would be better is to make the form's handle (and device context) properties, like VB does. I can't believe I just wrote that again, but it sure would solve problems like this one.

Thanks for the help.

George