>HEY MASSIVE THANKS TO YOU FOR YOUR HELP! What concerns me is that frm_ages is not a form in this project at all but in another project all together - I use the same base classes though - could it be possible that the class library is wonky here?

No, I think that was my fault, I was running the EXE you included, and that, apparantly, was wonky. Her is exactly what is happening, and what you can do about it:

In the form class, frm_DeskTop, there is an activex treeview. This has an activex event, NodeClick, which has some code in it that sets a form property to the NodeIndex. This event fires everytime you click a node (obviously). This includes double-clicking. Your DblClick event code and NodeClick code are firing at the same time, and in a sense, taking each other out.

( I've learned more about the treeview control doing this than I have ever wanted to, and the reason I say this is to make the point that I am not familiar with it, so I HOPE somebody has an answer. )

I verified the above assertation by calling the DblClick() method of the form from the NodeClick method of the treeview control, and everything works as expected, exactly how you want it. The only problem with this is that you lose your double click, and will need to move that code somewhere else, perhaps a custom method that is called from NodeClick. Or find some other way of setting the Forms.pNodeValue, rather than from the treeview's NodeClick event, which may be just about impossible to do, as the Node object doesn't seem to be exposed through the treeview control's interface.

The help file describes this problem as being associated with the AutoYield property of _VFP, however, I couldn't make it work with this property as either .T. or .F. I am using VFP7 to check this, though, maybe something is different in 6. Or maybe something is wrong with my setup here. Or maybe I don't know where I am supposed to put the DOEVENTS when AutoYield is .F. :) I hope that is the case, otherwise controls like this lose a lot of functionality.

It seems to me that the only solution is that you can't depend on the DblClick event of the treeview control to fire correctly with NodeClick, which would seem to me to be a major setback in the use of the treeview control. For reference, this happens with the Click event as well. NodeClick fires in tandem with DblClick, and with Click. That is pretty much all I have for you, Chris, I hope this helps you out.

Or you could use the

WAIT WINDOW "" TIMEOUT .5

in the mLaunchForm code right before it does the ZOOM NORM. Good luck with this, Chris.

jfh