I'm sorry if I was misleading...
I was referring to the MSDN Libray (on CD/DVD) and the VB6 documentation contained within that is part of the Visual Studio toolkit.
This info
is available online, but you need to know how to dig though the MSDN Libray (or get darned lucky on a search). The control you are using is not really meant for web development, it is intended as a VB control. But it works just fine in an HTA!
See:
This is the head reference for TreeView 6.0
The Object Browser is a very handy applet that functions within the IDEs (VB and InterDev) provided by Visual Studio. It lets you "peek inside" of object library files (.TLBs, .DLLs, .OCXs, etc.) and see the actual object model. It reveals the objects, methods, propeties, events, and constants within the library. It gives method parameter lists and everything - very useful.
I think even VB5 has an Object Browser.
One thing I must seriously recommend to anybody who doesn't have Visual Studio or at leaast VB, and who wants to use VBScript for
any purpose - desktop, server, or client - is to get your hands on VB 5 CCE (Control Creation Edition).
VB5CCE is FREE, is perfectly usable, and lets you build custom controls as well as explore pre-built ones. In some cases you may need to use a control from VBScript but you run into a problem with data types - script usually only handles Variants correctly. VB5CCE will let you "wrap" a control that script can't use directly with a type-matcher-upper that exposes a Variants-only interface to script and passes strong types to the pre-built jobbie-doo.
VB5CCE is really VB5 without the ability to save a compiled EXE (though it can save OCXs and such), some missing sets of MS controls, and shabby docs. That's the weakest part of VB5CCE - the docs (online Help).
You need to root around to find all the VB5 docs you will need as separate downloads.
Start here:
As an HTA developer you should be really jazzed about this. Remember I said you can't make an EXE with VB5CCE?
Well you can write practically a whole VB program as an OCX with one or more "UserControls" instead of VB forms, then invoke these together from your HTA which becomes the host for them. The HTA can be as fancy or as skeletal as you please.
Voila! Free VB development. {Please don't tell MS, anybody ;-)}