S
Steve Jorgensen
There are a large number of things I would like to do with code
introspection in VBA (MS Access), but the only ways I can find to do any
kind of introspection of a VBA project are using TLI (tlbinf32.dll), and
the only info I can get that way is about a class that I already have an
instance of.
So far, I cannot get any information about even a class module unless I
have other code that can generate an instance of it to pass to the TLI
functions, and I can't get info about non-class modules at all. What I can
do already is enough to write a VBA Unit tester, but it's not enough to do
some of the other things I'm itching to do.
Does anyone know how to take this to the next level?
Thanks,
- Steve J.
introspection in VBA (MS Access), but the only ways I can find to do any
kind of introspection of a VBA project are using TLI (tlbinf32.dll), and
the only info I can get that way is about a class that I already have an
instance of.
So far, I cannot get any information about even a class module unless I
have other code that can generate an instance of it to pass to the TLI
functions, and I can't get info about non-class modules at all. What I can
do already is enough to write a VBA Unit tester, but it's not enough to do
some of the other things I'm itching to do.
Does anyone know how to take this to the next level?
Thanks,
- Steve J.