Installed the OCX and took a look.

It appears that this takes every registered Class and presents it in the browse list. Most all of these classes are associated with a Type Library.

In other words, if you were to go into the TL Viewer and open each item in the browse list, everything shown in the "TypeInfos" column are the same objects that appear in the wshBrowse list. For example, there are dozens of CDO objects in the wshBrowser. All of them belong to the same type library. If you were to go into the TL Viewer Browser and select "Microsoft PKMCDO for Microsoft Web Storage System" (you may or may not have this on your machine) you would see under the "TypeInfos" list several dozen objects which correspond to the objects in the wshBrowser.

So the question becomes do you want an exhaustive list of all objects up front or do you want to browse individual type libraries. To me, it's a bit more useful to break it down into type libraries. If I'm doing work in ADSI or Excel or Access or whatever I'd rather see only objects related to those things than every possible object installed in my system.

Having said that though, if I'm in the minority on this issue I'd be happy to make the change.

What does everybody else think?

Steve

[ 03 July 2002, 00:16: Message edited by: Steve B ]
_________________________
Stevie