[RESOLVED] Multiple control OCX giving version trouble despite using Binary Compatibility

[sdouble_2]

I have figured out the problem. It wasn't as difficult as I made it out to be and was a bit silly.

These are the steps I took:
1. Compiled main executable to test with on my machine. Tried it, received same error as in first post.
2. Changed the license key in Licenses.Add for IHateThisThing.ThisOneSucks and recompiled main executable.
3. Ran main exe, new error: "No design-time license found for control 'IHateThisThing.ThisOneSucks'. Contact the vendor...."
4. Changed the license key back to what it was supposed to be and tried it all over again, back to the same error in from the first post. This made me look into the control's project a bit more. I found that it referenced another custom control itself that was a later version than what was installed on the production computers.
5. Changed the reference to TheOtherControl.OCX to the same version that was deployed and in production, recompiled IHateThisThing.OCX and everything was good.

So, what I learned is that VB6 wasn't able to follow the breadcrumbs to the other control and give me an error that mentioned "TheOtherControl.SomeInterface" and instead gave me a generic "VB.UserControl" error message. Maybe if IHateThisThing.OCX was actually referenced in the project, it would have been able to do so. Because of that, "VB.UserControl" tends to mean something outside of the immediate scope.