ActiveX - register new controls

I have an control that I updated from version 1.0.0 to version 1.1.0. I removed the old OCX by unregistering it then deleting it, then I set the new control in the SYSTEM directory and registered it. The problem is that Visual Basic would not load my old forms that used my old OCX. Why is that? I can go to COMPONENTS and then recheck the control and it works fine (though I have to add the control again to my form), but how am I suppose to update a control and not have to worry that Visual Basic will not load it?
microboardAsked:
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.

kamallCommented:
You MUST use either  'Binary compatibility' or 'Project compatibility' for your control. In the Project menu, select Project properties - component, and set the compatibility.
This will solve your problem and will update your control automatically when you reload your project that uses this control.
0
microboardAuthor Commented:
It didnt solve the problem. When I reload my project after updating my control in the SYSTEM directory, the error I get for my project is this:

The property name _ExtentX in AniCur1 is invalid.

This seems to be the big problem. I have the "Project Compatibility" set but for some reason it's not working the way I think it should be. Hope you can help solve this. Thanks.
0
manoj_rCommented:
Project compatibilty should be used when you are debugging your applications in the VB IDE.

When you want to release your second version of the component you should compile the project with Binary Compatibilty giving it the reference of your first version.

Refer to the article "Building, Versioning, and Maintaining Visual Basic Components" from MSDN which explains the differences. http://msdn.microsoft.com/library/techart/msdn_bldvbcom.htm

0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

manoj_rCommented:
Also look up
Providing a Reference Point for Binary Version Compatibility

http://msdn.microsoft.com/library/devprods/vs6/vbasic/vbcon98/vbconprovidingreferencepointforcompatibility.htm
0
microboardAuthor Commented:
manoj_r, the articles certainly were informative. Things seem to be working fine here now! I need to send you the points so propose an answer so that I can do the transferring.

Thanks
0
manoj_rCommented:
Project compatibilty should be used when you are debugging your applications in the VB IDE.

When you want to release your second version of the component you should compile the project with Binary Compatibilty giving it the reference of your first version.

Refer to the article "Building, Versioning, and Maintaining Visual Basic Components" from MSDN which explains the differences. http://msdn.microsoft.com/library/techart/msdn_bldvbcom.htm 
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
microboardAuthor Commented:
Thanks!
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.