Improve company productivity with a Business Account.Sign Up

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

Executable cannot upgrade to new ocx version

We have a large executable in the company (about 6MB) and I tried to take some of the new code outside to external object libraries. the problem is that the tests we conduct sometimes need an upgrade of the ocx when we discover a bug or need an additional feature. The problem is that no matter what compatibility settings have I tried to put, and although I tested it with another compilation only (with no changes what so ever from the previous compilation of the ocx) the IDE sees the ocx as a new version, and the executable won't accept it as a compatible component.
Correct me plaese if I have misundertood something on the way, but I think there should be a possibility to upgrade the controls without having to re-compile the executable each time.

More points are waiting for the answer I need.
0
zivf
Asked:
zivf
  • 2
1 Solution
 
idcanadaCommented:

The answer you need may not be a happy one, however, in such cases,
I would put every possible set back on my side.

1 DL VB Service Pack 2

2 Make sure the EXE does not depend on old Properties, Subs or Functions
that you have depricated in the newer version. (Might be your case)
Your EXE will keep its prior working version.

3 Set Binary Compability, (To keep same GUID) and build / make the OCX file.
Now, Rebuild the EXE.
Make sure EXE is useing the newer OCX file. (Check References or Components)

4 Of course, all this is better manageable if you have the OCX & EXE projects in a
Visual Basic Project Group.

5 If all fails, this solution will work, however quite dramatic.
Open EXE Project File with Notepad, manually remove your OCX file reference and Save.
Open your Project with VB, loads of errors, but not that bad since your OCX file now
becomes a PictureBox with the name you gave it.
Manually insert your OCX threw the components dialog and bowse threw each
form that had your control and add it again.
No code has changed, and none will if you take the name from the picture box that was created instead of your control.


Well, best of luck lad.

If you have tried these steps and still you do not get the result you are looking for,
try building a small sample with that control and test the upgrade.
(Instead of working with the 6mg EXE).
If you simply can not, I would remake the OCX under a different name.


0
 
zivfAuthor Commented:
I need to check this thing out. The reason I posted the question to experts-exchange was because I could not find any answer no matter what combination I tried. Whenever I will try + succeed you'll get your points and even some more I have.
Until then anyone that wants is invited to leave his/her comments here.
0
 
zivfAuthor Commented:
Thanks a lot! I came to understand that the key to the whole is the binary compatibility setting.
I was very close to give-up the whole component thing, from the desperation I been to.
Thanks again.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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