 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
John Guest
|
Posted: Fri Jul 02, 2004 7:05 pm Post subject: Referencing a component from a component |
|
|
I've looked around the various newsgroups and haven't found an answer to
this yet, so hopefully, I can get some help here.
I have two components, we'll call them CompA and CompB. Now these two
components both rely on a third component for their operation and we'll call
this SupportC.
If I install SupportC, then I can't install either CompA or CompB as they
both flag an error during the install process indicating that SupportC
already exists. So I remove SupportC and can install CompA or CompB but not
both, as when one is installed it will also install SupportC and then the
other component fails to install because it flags an error to indicate that
SupportC already exists.
I'm at a loss here. I know I should be able to do this, but some reason I
can't. Any suggestions on this would be greatly appreciated.
Thanks
|
|
| Back to top |
|
 |
Gerhard Müller Guest
|
Posted: Mon Jul 05, 2004 10:14 am Post subject: Re: Referencing a component from a component |
|
|
Hi John,
probably you try to register the "SupportC" component more then once.
A component will be registered with the function "RegisterComponents".
Usually this function is called inside another function named "Register"
at the end of the source code of the component.
If you try to register the same component twice, e.g. inside the source
file "SupportC" and also inside "CompA", such an error like you descripted
may occur.
The fact that you are able to install "CompA" without having installed
"SupportC" before tells me that my assumption could be right. Especially
because the attempt to install "CompB" after "CompA" also failed since
"CompB" tries also to register "SupportC".
I suggest to remove that part of souce code inside "CompA" and "CompB"
which registers the component "SupportC". Inside "CompA" should only
the component "CompA" be registered, inside "CompB" only the component
"CompB" and so on......
How ever, if this is not the reason for your problem, you should announce
an example of your source code. Then it will be easier to find a solution
for your problem.
Best regards
Gerhard
"John" <john (AT) nospam (DOT) com> schrieb im Newsbeitrag
news:<40e5b187$1 (AT) newsgroups (DOT) borland.com>...
| Quote: | I've looked around the various newsgroups and haven't found an answer
to this yet, so hopefully, I can get some help here.
I have two components, we'll call them CompA and CompB. Now these two
components both rely on a third component for their operation and
we'll call this SupportC.
If I install SupportC, then I can't install either CompA or CompB as
they both flag an error during the install process indicating that
SupportC already exists. So I remove SupportC and can install CompA
or CompB but not both, as when one is installed it will also install
SupportC and then the other component fails to install because it
flags an error to indicate that SupportC already exists.
I'm at a loss here. I know I should be able to do this, but some
reason I can't. Any suggestions on this would be greatly appreciated.
Thanks
|
"John" <john (AT) nospam (DOT) com> schrieb im Newsbeitrag
news:40e5b187$1 (AT) newsgroups (DOT) borland.com...
| Quote: | I've looked around the various newsgroups and haven't found an answer to
this yet, so hopefully, I can get some help here.
I have two components, we'll call them CompA and CompB. Now these two
components both rely on a third component for their operation and we'll
call
this SupportC.
If I install SupportC, then I can't install either CompA or CompB as they
both flag an error during the install process indicating that SupportC
already exists. So I remove SupportC and can install CompA or CompB but
not
both, as when one is installed it will also install SupportC and then the
other component fails to install because it flags an error to indicate
that
SupportC already exists.
I'm at a loss here. I know I should be able to do this, but some reason I
can't. Any suggestions on this would be greatly appreciated.
Thanks
|
|
|
| Back to top |
|
 |
John Guest
|
Posted: Mon Jul 19, 2004 12:38 pm Post subject: Re: Referencing a component from a component |
|
|
Thanks Gerhard,
it turned out that there was some lingering library pointers inside the .bpk
file. I opened up the file with a text editor, cleaned it up and that fixed
the problem.
I'm getting a little annoyed at how frequently I find myself modifying the
bpk or bpr files with a text editor.
John
--
"Gerhard Müller" <gerhard.mueller (AT) dlr (DOT) de> wrote
| Quote: | Hi John,
probably you try to register the "SupportC" component more then once.
A component will be registered with the function "RegisterComponents".
Usually this function is called inside another function named "Register"
at the end of the source code of the component.
If you try to register the same component twice, e.g. inside the source
file "SupportC" and also inside "CompA", such an error like you descripted
may occur.
The fact that you are able to install "CompA" without having installed
"SupportC" before tells me that my assumption could be right. Especially
because the attempt to install "CompB" after "CompA" also failed since
"CompB" tries also to register "SupportC".
I suggest to remove that part of souce code inside "CompA" and "CompB"
which registers the component "SupportC". Inside "CompA" should only
the component "CompA" be registered, inside "CompB" only the component
"CompB" and so on......
How ever, if this is not the reason for your problem, you should announce
an example of your source code. Then it will be easier to find a solution
for your problem.
Best regards
Gerhard
"John" <john (AT) nospam (DOT) com> schrieb im Newsbeitrag
news:<40e5b187$1 (AT) newsgroups (DOT) borland.com>...
I've looked around the various newsgroups and haven't found an answer
to this yet, so hopefully, I can get some help here.
I have two components, we'll call them CompA and CompB. Now these two
components both rely on a third component for their operation and
we'll call this SupportC.
If I install SupportC, then I can't install either CompA or CompB as
they both flag an error during the install process indicating that
SupportC already exists. So I remove SupportC and can install CompA
or CompB but not both, as when one is installed it will also install
SupportC and then the other component fails to install because it
flags an error to indicate that SupportC already exists.
I'm at a loss here. I know I should be able to do this, but some
reason I can't. Any suggestions on this would be greatly appreciated.
Thanks
"John" <john (AT) nospam (DOT) com> schrieb im Newsbeitrag
news:40e5b187$1 (AT) newsgroups (DOT) borland.com...
I've looked around the various newsgroups and haven't found an answer to
this yet, so hopefully, I can get some help here.
I have two components, we'll call them CompA and CompB. Now these two
components both rely on a third component for their operation and we'll
call
this SupportC.
If I install SupportC, then I can't install either CompA or CompB as
they
both flag an error during the install process indicating that SupportC
already exists. So I remove SupportC and can install CompA or CompB but
not
both, as when one is installed it will also install SupportC and then
the
other component fails to install because it flags an error to indicate
that
SupportC already exists.
I'm at a loss here. I know I should be able to do this, but some reason
I
can't. Any suggestions on this would be greatly appreciated.
Thanks
|
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|