Can't update NTEXT field on SQL2K...HELP!

[XMan]

Just porting the back-end to SQL2K tonight and ran into this major problem...When I try to update an NTEXT data type field I'm getting ODBC error from SQL2K saying this:

[Microsoft][ODBC SQL Server Driver][SQL Server]The text, ntext, and image data cannot be compared or sorted, except when using IS NULL or LIKE operator. [#306]

Is there a way to fix this? TIA.

 

[Michel Walsh]

Hi,


What Jet calls Text, MS SQL Server call it a varchar. What MS SQL Server
call a Text, Jet calls it a Memo. You can't group by on Memo in Jet, you
can't group by on Text in MS SQL Server. Access is not the problem, the
problem is that when you change of language, you should be cautious of
"false friend", words that are the same, but used completely differently, if
not completely the opposite, like "inflammable" in French (meaning
something you can, able, to put flame-in, flame into it ) and in English (
where in does not mean into, but means not, like something which is not
flammable). Text is one of these false friend between Jet and MS SQL
Server. Access is just the middle man, you were reedy to hang the wrong
culprit.


Hoping it may help,
Vanderghast, Access MVP


Just porting the back-end to SQL2K tonight and ran into this major
problem...When I try to update an NTEXT data type field I'm getting ODBC
error from SQL2K saying this:

[Microsoft][ODBC SQL Server Driver][SQL Server]The text, ntext, and image
data cannot be compared or sorted, except when using IS NULL or LIKE
operator. [#306]

Is there a way to fix this? TIA.

 

[Mike Sherrill]

On Thu, 13 Nov 2003 06:38:45 -0500, "Michel Walsh"

[snip]

when you change of language, you should be cautious of
"false friend", words that are the same, but used completely differently, if
not completely the opposite, like "inflammable" in French (meaning
something you can, able, to put flame-in, flame into it ) and in English (
where in does not mean into, but means not, like something which is not
flammable).

"Inflammable" seems to be a doubly false friend . . .