Click to See Complete Forum and Search --> : [VB6] Compile ActiveX Controls compatibles
joaquim
Nov 4th, 2009, 01:23 PM
what i'm doing is;
i have 1 groupproject for test my control. but for a complete test, i compile the control(*.ocx file) and use in other project.
if these new project has the control used and if i put another compile control(i'm speak the same control, but updated), why give an error. and for use it i must rebuilt(only change the controls in form).
how can i avoid these problem?
thanks
LaVolpe
Nov 4th, 2009, 02:59 PM
After you compile your control to an ocx, suggest:
1. Open the project and view project properties
2. Click on the Component tab in the properties window
3. Choose "Binary Compatibility"
4. Click the ellipsis button and select the OCX you just compiled
Now if you make minor changes and recompile, you should not have those problems. If you add or remove any Public properties or Public methods, you will break compatibility. If you change the parameters within any Public methods, you will break compatibility. When you break compatibility, your ocx will no longer be the same and will be a new version.
Recommend reading this regarding compatibility (http://pntpm3.ulb.ac.be/Info/Activex/ch25.htm#VersionCompatibility).
techgnome
Nov 4th, 2009, 03:11 PM
if you look in my sig, there's a link to a post " Set your VB6 ActiveX Compatibility" about binary compatibility, and how to use it effectively.
-tg
joaquim
Nov 4th, 2009, 03:50 PM
After you compile your control to an ocx, suggest:
1. Open the project and view project properties
2. Click on the Component tab in the properties window
3. Choose "Binary Compatibility"
4. Click the ellipsis button and select the OCX you just compiled
Now if you make minor changes and recompile, you should not have those problems. If you add or remove any Public properties or Public methods, you will break compatibility. If you change the parameters within any Public methods, you will break compatibility. When you break compatibility, your ocx will no longer be the same and will be a new version.
Recommend reading this regarding compatibility (http://pntpm3.ulb.ac.be/Info/Activex/ch25.htm#VersionCompatibility).
hi LaVolte;)
give me an error: "unable to set version component compatible:" and the path where is my OCX file(i deleted for try see if gives me the error, but give me error):(
LaVolpe
Nov 4th, 2009, 03:57 PM
You cannot delete the ocx or if you point to the wrong ocx, you will get those errors.
In techgnome's signature, he has a link which has a step by step method. Try that now.
Also, please spend a little time and read the compatibility information in the link I gave you. It will help you better understand why & what we are recommending.
joaquim
Nov 4th, 2009, 04:03 PM
You cannot delete the ocx or if you point to the wrong ocx, you will get those errors.
In techgnome's signature, he has a link which has a step by step method. Try that now.
Also, please spend a little time and read the compatibility information in the link I gave you. It will help you better understand why & what we are recommending.
i never work with these option, but i belive that resolve the problem;)
by testing;), i change the file path and don't give me the error ;)
(i will see your link, but i will try copy the entire manual(i sod the index);))
everytime that i compile the file, did i need do these again?
techgnome
Nov 4th, 2009, 04:32 PM
no. that's the point of Binary Compatibility. Follow the steps in my link, and read the stuff from LaVolpe... you shouldn't need to change it again, except in a few cases, but hopefully that isn't very often.
-tg
joaquim
Nov 4th, 2009, 04:36 PM
thanks to everyone.
for finish these topic, need ask anotherthing:
my control is compatible with other OOPL?
vbforums.com
Copyright Internet.com Inc., All Rights Reserved.