Hi Monty,

First of all, I would like to confirm my understanding of your issue.
From your description, I understand that you have a VB Project(e..g. A) ,
which will reference COM Library(e.g. B,C,D..).
Also you use tlbimp tool to generate a .NET interop library
MyCOMInterfaces_DotNet based on a COM library(e.g. X).
The Vb Project A will reference to the library MyCOMInterfaces_DotNet.

Now even if you have release all the references to the
MyCOMInterfaces_DotNet assembly, you still get the error message per your
post.
Have I fully understood you? If there is anything I misunderstood, please
feel free to let me know.

From the description, the VB Project will also register for COM Interop.
So far I think you may try to check if any of the code may underlying using
the Interface from the MyCOMInterfaces_DotNet or COM library X.

Also to isolate the problem, I suggest you try to create a new project and
add all the common reference to the COM(B,C,D...) but not COM X.
And copy/paste/add the file/code line into the new project one by one to
see if the problem persists and which file or code line cause the behavior?

Please try to the steps and let me know the result.

Best regards,

Peter Huang

Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.