There are articles on the MSKB you should read, that explain what happens when ADO deals with text/blob type data:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q200124&; http://support.microsoft.com/default.aspx?scid=kb;en-us;Q175239 (read the More Information section) http://support.microsoft.com/default.aspx?scid=kb;en-us;Q194975 Thus, I don't think you are running into a problem with .GetRows per se, but a problem that data access layers have dealing with reading data on the fly from a database where the size of the underlying data is unknown (eg with an adOpenForwardOnly cursor). Suggest you use .AppendChunk (as shown in one of the KB articles above). David Penton also has some sample code on his site (www.davidpenton.com). Check the list archives if you can't find it. Cheers Ken ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From: "Bill Lammey" <[EMAIL PROTECTED]> Subject: getrows() limitations? : Howdy all, : : I'm having a strange problem with a query only returning partial data. : It's a table with over 42 columns, some of them of type text. I'm : selecting only 42 of the fields, and I structure the query so that the : text fields are selected last, and in order. Using getrows populates an : array (41x0) with some but not all of the text type fields empty, and : the last one full. Figured my problem was of the text field order type, : but I'm sure I'm selecting them in order. Here's the real surprise, when : I build an array from the recordset by hand using the following code, it : looks just like the result of getrows(), but WITH THE MISSING DATA! Is : this something that I should have expected or is this a problem with : getrows() that might be new? : : heres the relevant code; (I'm using Win2K with all the latest and IIS5, : with the .NET sdk installed (hope that isn't the cause!) but these are : plain old .asp files.) : : : ... : set rsRecord = cnData.execute(Query) : : iRow = rsRecord.Fields.Count : : recordInfo = rsRecord.getrows '<-----Bad Guy : : dim RecordInfo2() : redim RecordInfo2(iRow - 1, 0) : : rsRecord.movefirst : d = -1 : for each fld in rsRecord.fields : d = d + 1 : scratch = fld.Value : RecordInfo2(d, 0) = trim(scratch) '<-----Good Guy : (after loop) : next : ... : : : A few searches here and there turned up no weaknesses or size : limitations on getrows, I'll continue to keep looking... : : Thanks in advance for reading this overly long post... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --- You are currently subscribed to activeserverpages as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED]
