[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 170
  • Last Modified:

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?
0
microboard
Asked:
microboard
  • 3
  • 3
1 Solution
 
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 new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
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
 
microboardAuthor Commented:
Thanks!
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now