Board index » delphi » Upgrading 7 to 7.1 will most likely get me fired...

Upgrading 7 to 7.1 will most likely get me fired...


2004-09-25 04:37:58 AM
delphi247
Most of our development here is against a 3rd party COM object, that in
Delphi 7.,0 worked beautifully. However, after suggestions from various
other developers, we upgraded to Delphi 7.1 and now all access to the 3rd
party com object is dead. As a doornail. No programs that access that COM
object work at all now. Every one of my projects is dead, and I am in
serious jeopardy of losing my job.
How can I revert back to the old Delphi 7.0? There's no way to un-install
just the update...
 
 

Re:Upgrading 7 to 7.1 will most likely get me fired...

JSheble writes:
Quote
Most of our development here is against a 3rd party COM object, that
in Delphi 7.,0 worked beautifully. However, after suggestions from
various other developers, we upgraded to Delphi 7.1 and now all
access to the 3rd party com object is dead. As a doornail. No
programs that access that COM object work at all now. Every one of
my projects is dead, and I am in serious jeopardy of losing my job.

How can I revert back to the old Delphi 7.0? There's no way to
un-install just the update...
Only way I can think of is to uninstall everything and then re-install
from original media. The inability to remove a patch was a limitation
of the MSI 2.0 install engine.
 

Re:Upgrading 7 to 7.1 will most likely get me fired...

Is there any way to determine what could be going wrong? it is certainly
something to do with how the TypeLib is created or how the app actually
accesses the the COM Object. These problems only occurred after upgrading
to 7.1, and re-importing the TypeLib. I uninstalled the 7.1, re-installed
the 7.0 but did not re-import the TypeLib, I used the *_TLB.pas file that
was created with the 7.1 update, and all access to the COM object still
failed. I re-imported in 7.0 and it started working again.
The COM Object in question was created in VB, and it is not a very good COM
object, but unfortunately I have no real choice in the matter, I have to use
it.
"Leo Saguisag (Borland)" <lsaguisag_at_borland_dot_com>writes
Quote
JSheble writes:

>Most of our development here is against a 3rd party COM object, that
>in Delphi 7.,0 worked beautifully. However, after suggestions from
>various other developers, we upgraded to Delphi 7.1 and now all
>access to the 3rd party com object is dead. As a doornail. No
>programs that access that COM object work at all now. Every one of
>my projects is dead, and I am in serious jeopardy of losing my job.
>
>How can I revert back to the old Delphi 7.0? There's no way to
>un-install just the update...

Only way I can think of is to uninstall everything and then re-install
from original media. The inability to remove a patch was a limitation
of the MSI 2.0 install engine.
 

Re:Upgrading 7 to 7.1 will most likely get me fired...

mE writes:
Quote
Is there any way to determine what could be going wrong? It's
certainly something to do with how the TypeLib is created or how the
app actually accesses the the COM Object. These problems only
occurred after upgrading to 7.1, and re-importing the TypeLib. I
uninstalled the 7.1, re-installed the 7.0 but did not re-import the
TypeLib, I used the *_TLB.pas file that was created with the 7.1
update, and all access to the COM object still failed. I re-imported
in 7.0 and it started working again.

The COM Object in question was created in VB, and it is not a very
good COM object, but unfortunately I have no real choice in the
matter, I have to use it.
Did you preserve a copy of the _TLB.pas file created by 7.1? If you
did, run a filecomp and see if there are any differences. You may have
found a bug in the type library importer.
 

Re:Upgrading 7 to 7.1 will most likely get me fired...

There are a whole slew of differences... lots & lots & lots & lots...
But most of them appear to be the order in which it lists the properties and
methods. Without spending too much time on it, it doesn't appear that the
declarations themselves are different, they just appear to be in different
places in the TLB file. Same COM Object, but the importer is reading it in
different order?
There could be other changes, but I really don't have the time to study this
as in depth as I would like.
"Leo Saguisag (Borland)" <lsaguisag_at_borland_dot_com>writes
Quote
mE writes:

>Is there any way to determine what could be going wrong? It's
>certainly something to do with how the TypeLib is created or how the
>app actually accesses the the COM Object. These problems only
>occurred after upgrading to 7.1, and re-importing the TypeLib. I
>uninstalled the 7.1, re-installed the 7.0 but did not re-import the
>TypeLib, I used the *_TLB.pas file that was created with the 7.1
>update, and all access to the COM object still failed. I re-imported
>in 7.0 and it started working again.
>
>The COM Object in question was created in VB, and it is not a very
>good COM object, but unfortunately I have no real choice in the
>matter, I have to use it.

Did you preserve a copy of the _TLB.pas file created by 7.1? If you
did, run a filecomp and see if there are any differences. You may have
found a bug in the type library importer.
 

Re:Upgrading 7 to 7.1 will most likely get me fired...

JSheble writes:
Quote
There are a whole slew of differences... lots & lots & lots & lots...

But most of them appear to be the order in which it lists the
properties and methods. Without spending too much time on it, it
doesn't appear that the declarations themselves are different, they
just appear to be in different places in the TLB file. Same COM
Object, but the importer is reading it in different order?

There could be other changes, but I really don't have the time to
study this as in depth as I would like.
Hmmm... I don't know what to say on this one. I didn't think order
would be significant but then again I am hardly a COM guru...
Have you tried asking around the COM newsgroups? Maybe some of the
people who hang out there would have a better understanding of what
could be happening...
--
Leo Saguisag
Delphi l10n engineer
 

Re:Upgrading 7 to 7.1 will most likely get me fired...

I've posted a message there today... guess I will wait and see... If it is an
issue in Delphi, I hope it is corrected before Diamondback is released...
"Leo Saguisag (Borland)" <lsaguisag_at_borland_dot_com>writes
Quote
JSheble writes:

>There are a whole slew of differences... lots & lots & lots & lots...
>
>But most of them appear to be the order in which it lists the
>properties and methods. Without spending too much time on it, it
>doesn't appear that the declarations themselves are different, they
>just appear to be in different places in the TLB file. Same COM
>Object, but the importer is reading it in different order?
>
>There could be other changes, but I really don't have the time to
>study this as in depth as I would like.

Hmmm... I don't know what to say on this one. I didn't think order
would be significant but then again I am hardly a COM guru...

Have you tried asking around the COM newsgroups? Maybe some of the
people who hang out there would have a better understanding of what
could be happening...

--
Leo Saguisag
Delphi l10n engineer