
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I have a .NET assembly I use for common functionality in various applications. I have created COM objects for several of the functions so that the assembly can be registered in VBA code. This works perfect fine in Microsoft Access 2007 - I am able to register the TLB file and utilize the functions. However, I am not able to get the file to register in Inventor VBA.
One notable difference is that when I register the reference through Microsoft Access, it finds it by browsing the C:\Windows\System32 directory even though the file physically resides in C:\Windows\SysWOW64. Access knows to look there to obtain assemblies for the appropriate bit architecture. But Inventor does not find the file when browsing C:\Windows\System32. If I manually point it to the SysWOW64 path, it fails to register the assembly. There's no error message, it just simply does not insert it into the list of registered components.
So there are obviously key differences between the VBA environment in Inventor versus the environment in Microsoft Office. Can somebody point me in the right direction?
Solved! Go to Solution.