>>You objtoclient() may not be needed if your ActiveX is directly contained by the form,
>
>It is.
>
>>You are also going to need to use the WINDOW clause because otherwise it'll be relative to the main VFP window.
>
>I saw that in the help. I wasn't sure what the WindowName would be. Is it the form Name?
>
>>You may want to look if there is an API function that will just move the mouse a delta number of pixels from where it is.
>
>I did see a _MousePos() API. I have to see if that will work (or if I can figure out how translate it to FoxPro code ;)
>
>>Although there's no guarantee that the popup menu displayed down and left from the mouse it might have opened up and right depending on where the form is on the screen.
>
>True, hadn't thought about that. Am I the only one who has ever had this problem. I would think shortcut menus in treeviews would be a pretty common thing.
>
>>How about just keyboarding a downarrow followed by an uparrow to activate the menu?
>
>Hoped that would work, but no joy.
>
Roi,

Would the absolute co-ordinates of the TreeView be helpful? If so, you can get them using the Foxtools function _GetWRect(). Since the TreeView has an hWnd property, you could use that, like this:

store 0 to lntop, lnleft, lnbottom, lnright
lnhwnd = MyTreeView.hwnd
= _GetWRect(lnHwnd, @lntop, @lnleft, @lnbottom, @lnright)