typeInfo nil

Blair,

I generated classes for a COM-based wrapper of some device drivers.  It
is working, but the AXInspectors are not being nearly as helpful as they
might be.  They show the various propery names, but can't access them,
complaining that the type library is not registered (which is probably
the case).  There are generated methods, and they work.  The typeInfo iv
is nil for the offending IDispatch subinstances (all of them AFAICT).

Any ideas re what might be wrong to make typeInfo nil?  I have tried to
manually register all DLLs etc. that might contain type info.  The
product's installer database might also contain some clues.

Assuming I can correct the problem (presumably by registering
something), would I need to regenerate the interfaces to get them to
find the type library?

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]

"Bill Schwab" <[hidden email]> wrote in message
news:nADEe.3639$[hidden email]...
You should just be able to re-register the type-library using the command on
the additional tools menu. Bear in mind that the missing library might be
one that was referenced from the original library you generated. You can use
OLEVIEW to show these - Dolphin's IDL printing doesn't include the
information.

Regards

Blair

Blair,

> You should just be able to re-register the type-library using the command on
> the additional tools menu. Bear in mind that the missing library might be
> one that was referenced from the original library you generated. You can use
> OLEVIEW to show these - Dolphin's IDL printing doesn't include the
> information.

FWIW, the type OLEVIEW does not show the type library in its list of
type libraries.  That is after having (supposedly successfully)
registered it 2^n<g> times.  I am somewhat suspicious of a conflict
between two versions of their COMponents, and have called the missing
type library to their attention.

Have a good one,

Bill


--
Wilhelm K. Schwab, Ph.D.
[hidden email]