Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: Install Indy 9.0 on BCC 6 Professional returns Error from Package dclindy60.bpl
39 views
Skip to first unread message
Lynn
Sep 27, 2004, 4:06:05 PM9/27/04
to
I had same problem. Can you tell me how to clean indy 8 from bc++ 6?
Thanks
Lynn
"Elmar Baumann" <elmar-...@arcor.de> wrote:
>Ok, thanks you for Information, now it is running excellent !!
>
>Thanks
>
>Elmar
>
>
>
>"Remy Lebeau (TeamB)" <gambit47...@no.spam.yahoo.com> schrieb im
>Newsbeitrag news:408d...@newsgroups.borland.com...
>>
>> "Elmar Baumann" <elmar-...@arcor.de> wrote in message
>> news:408d6655$1...@newsgroups.borland.com...
>>
>> > i'm trying to install Indy 9.0 Components my C++Builder 6
>> > and get an Error when i do ..Install Packages/Add/dclIndy60.bpl.
>> > BCC6 returns "ProcedureEntryPoint "@Idresourcestrings@_RSBindingAny"
>> > in DLL "Indy60.bpl" not found".
>>
>> BCB6 ships with Indy 8, which is not compatible with Indy 9. The error is
>> caused by you still having old Indy 8 files on your machine. Please read
>> the Knowledge Base on Indy's website for install instructions.
>>
>>
>> Gambit
>>
>>
>
>
Jerome Hanby
Oct 8, 2004, 11:54:07 AM10/8/04
to
The basic answer to your question is to use your Borland Install CD to
remove Indy then install Indy 9. One thing you may want to consider.
If you have produced any software that is out of your control (say on
a user's pc) that uses the version of indy that you are upgrading and
that customer installs software built with the new version of Indy you
will break the old software. For whatever reason, the version of Indy
that comes with CBuilder 6 uses indy60.bpl. The version of Indy 9 that
you download, build, and install also produces an indy60.bpl. These
two BPLs are NOT compatible and the older software will no longer work
once you overlay it's indy60.bpl. To avoid this problem I changed the
build files for Indy 9 to produce indy69.bpl. My idea was to keep both
numbers as a reminder. While this solved the above problem, I didn't
catch that I may have picked a poor name for the file, so you may want
to use indy96 <g>.
remove Indy then install Indy 9. One thing you may want to consider.
If you have produced any software that is out of your control (say on
a user's pc) that uses the version of indy that you are upgrading and
that customer installs software built with the new version of Indy you
will break the old software. For whatever reason, the version of Indy
that comes with CBuilder 6 uses indy60.bpl. The version of Indy 9 that
you download, build, and install also produces an indy60.bpl. These
two BPLs are NOT compatible and the older software will no longer work
once you overlay it's indy60.bpl. To avoid this problem I changed the
build files for Indy 9 to produce indy69.bpl. My idea was to keep both
numbers as a reminder. While this solved the above problem, I didn't
catch that I may have picked a poor name for the file, so you may want
to use indy96 <g>.
"Lynn" <l...@eagency.com> wrote in message news:<415872ad$1...@newsgroups.borland.com>...
0 new messages