PDA

View Full Version : Custom OCXs do not register after version info was changed.



NewsArchive
10-25-1996, 12:00 AM
Dear InstallShield,
We have modified version information in all custom OCXs and now ISXPRO1.1
does not register them during installation. The registering was working
fine before we change version numbers from 1, 0, 0, ? to 1,1,0,0.
We have also changed the version string from 1,0,0,? to 1.10. (commas also
were replaced with periods).
That is all (we think) that was changed.
All OCXs are OLESelfRegister.
We did try to remove OCXs from the target machine and Regclean(ed) it, but
it did not help.

What exactly the rules (version checking and etc.) that govern the
registration process and what do we have to do to correct the problem?

Your prompt response will be greatly appreciated.

Oleg Goldfayn
Mercom
Oleg.Goldfayn@mercom.com

NewsArchive
01-11-1997, 01:00 AM
Oleg Goldfayn wrote:
>
> Dear InstallShield,
> We have modified version information in all custom OCXs and now ISXPRO1.1
> does not register them during installation. The registering was working
> fine before we change version numbers from 1, 0, 0, ? to 1,1,0,0.
> We have also changed the version string from 1,0,0,? to 1.10. (commas also
> were replaced with periods).
> That is all (we think) that was changed.
> All OCXs are OLESelfRegister.
> We did try to remove OCXs from the target machine and Regclean(ed) it, but
> it did not help.
>
> What exactly the rules (version checking and etc.) that govern the
> registration process and what do we have to do to correct the problem?
>
> Your prompt response will be greatly appreciated.
>
> Oleg Goldfayn
> Mercom
> Oleg.Goldfayn@mercom.comOleg Goldfayn wrote:
>
> Dear InstallShield,
> We have modified version information in all custom OCXs and now ISXPRO1.1
> does not register them during installation. The registering was working
> fine before we change version numbers from 1, 0, 0, ? to 1,1,0,0.
> We have also changed the version string from 1,0,0,? to 1.10. (commas also
> were replaced with periods).
> That is all (we think) that was changed.
> All OCXs are OLESelfRegister.
> We did try to remove OCXs from the target machine and Regclean(ed) it, but
> it did not help.
>
> What exactly the rules (version checking and etc.) that govern the
> registration process and what do we have to do to correct the problem?
>
> Your prompt response will be greatly appreciated.
>
> Oleg Goldfayn
> Mercom
> Oleg.Goldfayn@mercom.comOleg Goldfayn wrote:
>
> Dear InstallShield,
> We have modified version information in all custom OCXs and now ISXPRO1.1
> does not register them during installation. The registering was working
> fine before we change version numbers from 1, 0, 0, ? to 1,1,0,0.
> We have also changed the version string from 1,0,0,? to 1.10. (commas also
> were replaced with periods).
> That is all (we think) that was changed.
> All OCXs are OLESelfRegister.
> We did try to remove OCXs from the target machine and Regclean(ed) it, but
> it did not help.
>
> What exactly the rules (version checking and etc.) that govern the
> registration process and what do we have to do to correct the problem?
>
> Your prompt response will be greatly appreciated.
>
> Oleg Goldfayn
> Mercom
> Oleg.Goldfayn@mercom.comOleg Goldfayn wrote:
>
> Dear InstallShield,
> We have modified version information in all custom OCXs and now ISXPRO1.1
> does not register them during installation. The registering was working
> fine before we change version numbers from 1, 0, 0, ? to 1,1,0,0.
> We have also changed the version string from 1,0,0,? to 1.10. (commas also
> were replaced with periods).
> That is all (we think) that was changed.
> All OCXs are OLESelfRegister.
> We did try to remove OCXs from the target machine and Regclean(ed) it, but
> it did not help.
>
> What exactly the rules (version checking and etc.) that govern the
> registration process and what do we have to do to correct the problem?
>
> Your prompt response will be greatly appreciated.
>
> Oleg Goldfayn
> Mercom
> Oleg.Goldfayn@mercom.com

I read your appeal to the vendor for some explanation about controls not registering. I
have a similar experience that may shed some light on this...
I had many problems with Crystal Reports (CRYSTL16.OCX) not registering because that
vendor released a fix without incrementing the version string. Hence, the version
checking done by install products such as Installshield properly did not replace the OCX
in the target machine.

Seagate, the Crystal vendor, admitted this was their problem and used a Borland utility
to "zap" the version string from 1.0.0.34 to 1.0.0.36. I am not familiar with that
process but I am now having problems registering this OCX.

Unfortunately, Installshield gives no notice at the time of the install, but at runtime
I get a message: "Can't load (or register) custom control CRYSTL16.OCX".

Your experience sounded like mine. I wonder if you learned anything more since your
original posting of the issue ?