On Thu, 29 Mar 2007 10:08:12 +1000, Jon Tveten
<jonsnews@netspace.net.au> wrote:
>In article <f2sl03ptb9tfm86van2tnhbitsgn6dh79g@4ax.com>,
>bo.berglund@telia.com says...
>> Maybe that it is not installed in a comopnent palette tab? Well, I
>> tried to edit a package file but to no avail (the edit button is
>> greyed out on all packages). So I tried creating a new package
>> "BorlandOldSockets" and added the ScktComp.pas file to that package
>> and tried to build it. Now Delphi complains that the rtl already
>> contains ScktComp!!!!
>> So why does it not find it when I am checking my old application?
>>
>> Very strange. Help appreciated!
>> /Bo
>>
>
>Have you tried to install the dclsockest100.bpl packet (you will find it
>in the BIN dir.)
>
Thanks, now that message does not pop up anymore.
Next problem is getting my Indy things to work. BDS2006 ships with
Indy10 and Delphi7 used Indy9 so now I am stuck with incompatibilities
for the IdSmtp component.
I use this in order to send messages from a server when certain
monitored items trigger. Worked fine in Delphi7 but now doesn't even
compile. :-(
And I must make my code buildable on both BDS2006 and Delphi7.
Is there any way to put in conditionals to detect BDS2006 versus
Delphi7 and use different sourcelines for each?
Right now it stops on this line:
IdSendMail.AuthenticationType := IdSmtp.atLogin;
If I change it to something like:
{$IFDEF DELPHI7}
IdSendMail.AuthenticationType := IdSmtp.atLogin;
{$ENDIF}
{$IFDEF BDS2006}
IdSendMail.AuthType := IdSmtp.???; (what to use here?)
{$ENDIF}
Note that I do not have a form where these components are dropped,
they are all created in the class constructor of my handler...
/Bo
