DW 8.02/CS3 and SQL ntext fields

[CampHeato]

I am having trouble with ntext fields showing up in my pages. When I test the query inside DW, a single record will show the ntext field value as undefined. If I test a query that returns multiple records, the ntext field value is undefined for the first record, but the other records have the correct values for the ntext field.

I actually found a post that I did 14 months ago in a DW forum, and I answered my own question with a CursorType of 2 or 3. However, DW CS3 commands do not allow this, so now I am back to needing a solution.

I am using the ASP/VBScript Server Model on IIS and Microsoft SQL Server 2000 - 8.00.2039 (Build 3790: Service Pack 1)

[Newsgroup_User]

In your recordset, is the "ntext" field being called last?




"CampHeato" <webforumsuser@macromedia.com> wrote in message
news:f3b13e$4md$1@forums.macromedia.com...
>I am having trouble with ntext fields showing up in my pages. When I test
>the
> query inside DW, a single record will show the ntext field value as
> undefined.
> If I test a query that returns multiple records, the ntext field value is
> undefined for the first record, but the other records have the correct
> values
> for the ntext field.
>
> I actually found a post that I did 14 months ago in a DW forum, and I
> answered
> my own question with a CursorType of 2 or 3. However, DW CS3 commands do
> not
> allow this, so now I am back to needing a solution.
>
> I am using the ASP/VBScript Server Model on IIS and Microsoft SQL Server
> 2000
> - 8.00.2039 (Build 3790: Service Pack 1)
>

[CampHeato · Accepted solution]

I found this Tech Note, http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=kb00153 after many hours of searching the web. To answer your question, the NTEXT field is now last in the SQL connection, and that solved the problem. The other alternative, so that I did not have to change select statements in all of my queries, was to move the NTEXT field to the last in the table. That way, the SELECT * will work.

The Tech Note suggests a custom connection string, but I have not tried that to see what impact that has.

[Newsgroup_User]

Glad it worked, using SELECT * is not the best thing to do as far as
efficiency.

"CampHeato" <webforumsuser@macromedia.com> wrote in message
news:f3hnqp$8hu$1@forums.macromedia.com...
>I found this Tech Note,
> http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=kb00153 after many
> hours of searching the web. To answer your question, the NTEXT field is
> now
> last in the SQL connection, and that solved the problem. The other
> alternative,
> so that I did not have to change select statements in all of my queries,
> was to
> move the NTEXT field to the last in the table. That way, the SELECT * will
> work.
>
> The Tech Note suggests a custom connection string, but I have not tried
> that
> to see what impact that has.
>