Re: The data types varchar and text are incompatible in the equal to operator

Stephan, thx!

Hmmm...Sounds good...I'll try!

For Stefan to Stephan...My name is Adam Stefan(!!!) Costa :D

It's a good sign!

"Stephan Haidinger" <noxspamhaidinger@xxxxxx> wrote in message
news:455b2fef@xxxxxxxxxxxxxxxxxxxxxxxxx
don't know if it's the same
but I had to set param.size := 1 for empty string param values (default
was zero)
maybe you can try this

"AdamStefanCosta" <adam9000@xxxxxxxxxxxxxx> wrote in message
news:4554e77d@xxxxxxxxxxxxxxxxxxxxxxxxx
I found in Tamaracka anyone that get the same error...in the same
circustances:

Subject:

"ADO Changing varchar to text when NULL supplied"

Is posted in 05/24/2002, with no resolutions :S

Article number: 3555500


"Kevin Frevert" <kevin@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4554d221$1@xxxxxxxxxxxxxxxxxxxxxxxxx
Adam,

I don't know exactly where it is (an issue with ADO? Midas?), but a
workaround is to use the keyword LIKE instead (tested using D6/MSSQL
2005/ADO 2.8).

Ex. (CommandText property of a TADODataSet at design time)

Select Something
From SomeTable
Where SomeValue LIKE :SomeValue

In Delphi (opening the clientdataset)

Param[0].Value := SomeStringValue;

Good luck,
krf

"AdamStefanCosta" <adam9000@xxxxxxxxxxxxxx> wrote in message
news:45548519@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Community

In a MIDAS application, TClientDatasets with String params set equal to
blank (...param[0].value='') generates the follow error when I convert
my ApplicationServer to ADO:

"The data types varchar and text are incompatible in the equal to
operator"

In BDE this error do not exists...

Are there some parameter in ADO Connection String to supress this
error? Are ansi null related problem???

SQLServer2k5 | ADO Broker (D7) | ISAPI InternetExpress (D5)

Thx in Advance...









.

Relevant Pages