I'm trying to create a reference to an ocx via vb's reference dialog.  The
ocx (no .tlb is provided) is not listed so I browse for, and select it.
Upon selecting the ocx, vb hangs with 100% processor useage.  After this,
the ocx has been rendered useless, and must be reinstalled.

Q:  Am I required to have the .tlb file in order to create a reference?
Before this I was of the belief that all of the type info is built into the
ocx as a resource.

Any help greatly appreciated.

You shouldn't need the .TLB but you will need to have all the required
support DLL's. In addition, they, just like the OCX, will need to be
registered properlly if they are OLE DLL's.

The installation routine for the OCX should be taking care of all of this,
but if not you might try using "(regsvr32 Location)\regsvr32 (Full Path to
OCX)". On Windows 95 regsvr32 is in the \Windows\system directory usually,
and on WinNT it is in the \WinNT\System32 directory. The end result is that
you may get something like:

C:\WinNT\Systems32\regsvr32 c:\winnt\system32\control.ocx

Running that is the best way to register OCX's that I know of. I find
regsvr32 so useful that I always add it to my send to list so that I can
just right-click on an ocx and send it to regsvr32 to register it.

Hope this helps,
Peter Stambaugh

Hi Peter
    I have tried using the regsvr32 to register gauge32.ocx, and though it
reports success, when I try to use the control it says its not registered.
Any ideas, I think there are quite a few people having this trouble.
Thanks John
will need to be

Not many. If regsvr32 reports success it should be properly registered.

It could be a license issue however. A control could be registered for
run-time only if the license file had been deleted or something. I don't
have the gague32.ocx file on my disk so I can't try it out.

I remember seeing it in the past though, is it part of a package?

Peter