Error » Error News and Info » Knowledge Base » strange problem - recordset query loses data after response.write

Knowledge Base Most common error and how to trouble shoot them off

Post New Thread Reply
  strange problem - recordset query loses data after response.write
LinkBack Thread Tools Display Modes
Old 22-May-2007, 08:10 AM   #1 (permalink)
Fixed Error!
 
driverdownloads's Avatar

Posts: 1,672
Join Date: Mar 2007
Rep Power: 3 driverdownloads is on a distinguished road

IM:
Default 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?
driverdownloads is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit!
Reply With Quote
   


   
Old 22-May-2007, 08:10 AM   #2 (permalink)
Fixed Error!
 
driverdownloads's Avatar

Posts: 1,672
Join Date: Mar 2007
Rep Power: 3 driverdownloads is on a distinguished road

IM:
Default Re: strange problem - recordset query loses data after response.write

do not use the .Recordcount property unless really needed, because it is 1) not relyable 2) should not be needed anyhow.

you migh try this:

response.write adorecordset.recordcount
adoRecordset.Movefirst
Do Until adoRecordset.EOF

but you might run into another error, ie like "provider does not support move..."



tip:
instead of

Set adoRecordset = adoCommand.Execute

try this:

Set adoRecordset = Server.CreateObject("ADODB.Recordset")
adoRecordset.open adoCommand


question:
what database?
why did you post ing Windows 2003 Active Directory?
driverdownloads is offline  
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit!
Reply With Quote
Post New Thread Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT -8. The time now is 03:14 PM.

Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0

DMCA Policy

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227