Error - View Single Post - strange problem - recordset query loses data after response.write

**driverdownloads** · 22-May-2007, 09:10 AM

Question: I have this strange problem under asp, when using recordset query, its like the response.write sucks the information out of the varible permantley???

' Run the query.
Set adoRecordset = adoCommand.Execute

' Enumerate the resulting recordset.
response.write adorecordset.recordcount <<< this returns the correct value of 9, however if this line is enabled the next line doesn't work

Do Until adoRecordset.EOF <<< if the above line is commented out, this will run, if its not this fails ADODB.Recordset (0x800A0BCD) Either BOF or EOF is True, or the current record has been deleted. Requested
operation requires a current record

which means the data doesn't exist after i do a response.write? how come how do i keep it set untill i clear it? if i run the query again for a second time after the response.write it will work, but the query is complex and i dont want to run it twice in the same page just to find the same information out, how can i fix this?

22-May-2007, 09:10 AM	#1 (permalink)
driverdownloads Fixed Error! Posts: 1,672 Join Date: Mar 2007 Rep Power: 3 IM:	strange problem - recordset query loses data after response.write Question: I have this strange problem under asp, when using recordset query, its like the response.write sucks the information out of the varible permantley??? ' Run the query. Set adoRecordset = adoCommand.Execute ' Enumerate the resulting recordset. response.write adorecordset.recordcount <<< this returns the correct value of 9, however if this line is enabled the next line doesn't work Do Until adoRecordset.EOF <<< if the above line is commented out, this will run, if its not this fails ADODB.Recordset (0x800A0BCD) Either BOF or EOF is True, or the current record has been deleted. Requested operation requires a current record which means the data doesn't exist after i do a response.write? how come how do i keep it set untill i clear it? if i run the query again for a second time after the response.write it will work, but the query is complex and i dont want to run it twice in the same page just to find the same information out, how can i fix this?