The link to the ASPFAQs is at the top right corner of most every page on this site, including this one.<BR><BR>This FAQ is either in Databases, Errors category or Databases, General category. Or do a SEARCH for "Memo".<BR><BR>
http://www.aspfaqs.com/aspfaqs/ShowFAQ.asp?FAQID=80<BR><BR>This isn't quite as relevant, but it describes exactly the same fix:<BR>http://www.aspfaqs.com/aspfaqs/ShowFAQ.asp?FAQID=138<BR><BR>Two principles:<BR><BR>SELECT must have the long field last in its list.<BR><BR>Don't try to get the value from the RS more than once. Even to test whether or not it is blank. Assign it to a variable and then use the variable for all further work with the value.<BR>
still no luck!<BR><BR>I m using a SQL Server 7.0 database on NT4 with a varchar field 0f length 1800. I have seen an article that suggests that it is an NT4 issue. It seemed to work fine for someone in Windows 2000. Is this possible?? and if so there has got to be a workaround. I have included the varchar field a s the las in the select stmt, I have saved its value to a variable. Any more ideas??
It's really ugly, but I suppose one thing you could do is return the field as 8 chunks of 250 characters each, using the various string functions of SQL Server.<BR><BR>Then tack them back together in ASP code.<BR><BR>