Windows ME and VB6?


Does anybody know what this error means?

run-time error '374'.  Failed to activate control 'VB.UserControl'.
This control may be incompatible with your application.  Make sure that you are using the version of the control that was provided with your application.

Of course, I see what it says, but don't understand why it's happening.  I have a form with a few controls on it, but one of them is an OCX that I wrote myself.  The control is not named "UserControl", first of all, so I'm already confused!

Of my entire application, this is the only one having this problem, although, there aren't any other forms using that OCX I mentioned.

To complicate matters, this works on Win 95/98/NT.  It's only a problem on one of my users who's running ME.

Is there something special about Windows ME and custom OCX's?   Even a hint of what to start looking for?
u42093Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Anthony PerkinsCommented:
Take a look at this article on MSDN:
PRB: Error Messages When Recompiling ActiveX Component with Binary Compatibility (Q258192)
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
damienmCommented:
I don't know if this is relevant but it is from Microsoft  site.

http://support.microsoft.com/support/kb/articles/Q258/1/92.ASP
0
u42093Author Commented:

Oh, it had to be a Binary Compatiblity issue!!!!   That actually sounds like it might be it.  Gonna recompile and redeploy that control and see if that fixes things.

If it works, and since you both (acperkins and damienm) replied practically simultaneously, you both get the points!
0
PeteDCommented:
This is entirely down to compatibility! You must ensure that the other users machines have the same ocx version registered as the one that is compiled into your exe!.....otherwise you will get this error!
0
u42093Author Commented:

Thanks!  That was it!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.