Skip to main content
Y
yoderd1956
Participant
April 14, 2006
Question

CFMX and NTEXT fields

  • April 14, 2006
  • 1 reply
  • 460 views
I have a SQL table that includes 2 NTEXT fields. When I do a cfquery such as SELECT * FROM MYFILE, I get no value back for these fields. Playing around with it a bit more, the only way I've been able to get values back is if I list all the fields (rather than the metacharacter *) and then only if the NTEXT fields are the last ones in the list.

Is there some other way to deal with these fields in CFMX? Server settings? Options? The only NTEXT stuff I've really seen is about having to pre-pend an "N" in front of the value when using CFQUERY to update the field. Haven't found anything on pure select.

Note that this query works fine under CF5, but is giving me fits under CFMX.

Thanks, in advance, for any help you can give.

This topic has been closed for replies.

1 reply

S
SafariTECH
Inspiring
April 17, 2006
How big are the NTEXT fields' data?

Anything over a certain size requires that CLOB (Long Text Retrieval) be enabled in the datasource in the CF Administrator. ( I think it's actually required anyway if you use NTEXT at all, but I can't remember exactly.). It is OFF by default.

NTEXT really isn't recommended unless you have no alternative or have no idea how long the text could be ( and may exceed NVARCHAR's limits). NVARCHAR with a high limit value will generally work better.

Y
yoderd1956Author
Participant
April 24, 2006
Size varies. I believe we originally had nvarchar of 2000 and then someone blew through that and instead of making it a bigger nvarchar field, it was changed to the ntext. Had worked fine till we loaded CFMX and I started testing the page.

We checked the CLOB option but this doesn't seem to have made a difference. That is, if I do select * from.... I still get nothing back for my ntext fields, but if I list all fields in the select statement, making sure the ntext fields are last, I get the data without a hitch.
A
Anonymous
May 31, 2006
I'm having the same problem... any solutions? I'm using SQL Server 2005 Express.
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices