Re: D5 + SQLSERVER
- From: "Vitali Kalinin" <vitkalinin@xxxxxxxxx>
- Date: Fri, 19 May 2006 12:55:32 +0300
AdoConnection.Execute('SET CONCAT_NULL_YIELDS_NULL OFF');//switch it off to
simulate BDE
AdoConnection.Execute('SET CONCAT_NULL_YIELDS_NULL ON');//switch it on again
Still better would be to adopt yours SQL to process nulls gracefully. For
example you can use this construct: IsNull(<COLUMN_NAME>, '')
"Jean-Michel Granier" <jmgway@xxxxxxx> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ
ÓÌÅÄÕÀÝÅÅ: news:446d85b3@xxxxxxxxxxxxxxxxxxxxxxxxx
Vitali,
do you have an example to use this option in ado ?
Thank you
JM
"Vitali Kalinin" <vitkalinin@xxxxxxxxx> a écrit dans le message de
news:446d7de9$1@xxxxxxxxxxxxxxxxxxxxxxxxx
play
"Jean-Michel Granier" <jmgway@xxxxxxx> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ
ÓÌÅÄÕÀÝÅÅ: news:446d7bae@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello Vitali,Sure it is same since QA use ODBC, thus assigns CONCAT_NULL_YIELDS_NULL
no the problem is the same inside SqlAnalyser (sqlserver 2005).
regards,
Jean-Michel
to
ON, which is done by OLEDB provider also, but not done by BDE. You can
with Connection Properties in QA switch off "Set concat_null_yields null"
and see if it will make any difference.
.
- References:
- Re: D5 + SQLSERVER
- From: Jean-Michel Granier
- Re: D5 + SQLSERVER
- From: Vitali Kalinin
- Re: D5 + SQLSERVER
- From: Jean-Michel Granier
- Re: D5 + SQLSERVER
- Prev by Date: Re: Flow Control in Access?
- Next by Date: Re: Flow Control in Access?
- Previous by thread: Re: D5 + SQLSERVER
- Next by thread: Flow Control in Access?
- Index(es):
Relevant Pages
|