Since the december update of CB2007 I always get the exception "Property
SASL mechanism does not exist". I made a form with an TIdSMTP component.
When the form is created I get this exception.

Here is a sample code:

TTestForm::TTestForm(TComponent* Owner):
	TForm(Owner)	// <--- In this line occurs the exception
{
....
}

Any workarounds?

I looked also what the IDE is linking and it links indy10. All paths are 
to Indy10 (like lib\indy10 and so on).

Remy Lebeau (TeamB) schrieb:
> "riweber"  wrote in message 
> news:477764ba$1@newsgroups.borland.com...
> 
>> How can I check which version I have.
> 
> Unfortunately, it is not that simple in this case.  The compiler is pulling 
> in a different version of Indy at compile-time than what the IDE is using at 
> design-time.  You have multiple versions in your path settings, and the 
> compiler is finding the wrong one.  The component works at design-time 
> because the IDE knows which packages it was told to load.  So make sure your 
> path settings are configured properly.  At the very least, make sure the 
> Indy 10 folders are specified before the Indy 9 folders.
> 
>> I did a search and the .bpi and .lib files are all from december 2007...
> 
> That does not mean anything.  The timestamps could have just been updated.
> 
> 
> Gambit 
> 
> 

My problem is that I only find one version if I make a search over all
paths (with the Windows seearch function I type in
*indy*.bpl;*indy*.bpi). All found files have the same dates/times...
Can it be that CB2007 links the files of Indy6 (that are on the same
Harddisk) from BCB6?

Remy Lebeau (TeamB) schrieb:
> "riweber"  wrote in message 
> news:477764ba$1@newsgroups.borland.com...
> 
>> How can I check which version I have.
> 
> Unfortunately, it is not that simple in this case.  The compiler is pulling 
> in a different version of Indy at compile-time than what the IDE is using at 
> design-time.  You have multiple versions in your path settings, and the 
> compiler is finding the wrong one.  The component works at design-time 
> because the IDE knows which packages it was told to load.  So make sure your 
> path settings are configured properly.  At the very least, make sure the 
> Indy 10 folders are specified before the Indy 9 folders.
> 
>> I did a search and the .bpi and .lib files are all from december 2007...
> 
> That does not mean anything.  The timestamps could have just been updated.
> 
> 
> Gambit 
> 
> 

"riweber"  wrote in message 
news:477764ba$1@newsgroups.borland.com...

> How can I check which version I have.

Unfortunately, it is not that simple in this case.  The compiler is pulling 
in a different version of Indy at compile-time than what the IDE is using at 
design-time.  You have multiple versions in your path settings, and the 
compiler is finding the wrong one.  The component works at design-time 
because the IDE knows which packages it was told to load.  So make sure your 
path settings are configured properly.  At the very least, make sure the 
Indy 10 folders are specified before the Indy 9 folders.

> I did a search and the .bpi and .lib files are all from december 2007...

That does not mean anything.  The timestamps could have just been updated.


Gambit 

How can I check which version I have. I did a search and the .bpi and
..lib files are all from december 2007...

Remy Lebeau (TeamB) schrieb:
> "riweber"  wrote in message 
> news:4774d15a$1@newsgroups.borland.com...
> 
>> Since the december update of CB2007 I always get the
>> exception "Property SASL mechanism does not exist".
> 
> SASLMechanisms is an Indy 10 property.  Your DFM contains a reference to the 
> property, but your application is not linked to a version of the Indy 
> library that contains that property in its RTTI.  So you are likely linking 
> to Indy 9 instead of 10.
> 
> 
> Gambit 
> 
> 

"riweber"  wrote in message 
news:4774d15a$1@newsgroups.borland.com...

> Since the december update of CB2007 I always get the
> exception "Property SASL mechanism does not exist".

SASLMechanisms is an Indy 10 property.  Your DFM contains a reference to the 
property, but your application is not linked to a version of the Indy 
library that contains that property in its RTTI.  So you are likely linking 
to Indy 9 instead of 10.


Gambit