I understand this now, but I'm not sure if I'm going at what I need to do correctly. I have a search page, that times out on the sql end. I basically was going to use a Transaction that could be rolled back if the timeout i set was met. would this be the best way to go..using a transaction? is there a way to set a non-forward only mode since I'm only doing a select?
...talks about that:<BR><BR>http://support.microsoft.com/default.aspx?scid=/Support/ActiveServer/faq/data/adofaq.asp<BR><BR>It says you *will* timeout if you mix forward-only with a transaction.<BR><BR>Can you change the mode? Of course!<BR><BR><%<BR>Set RS = Server.CreateObject("ADODB.RecordSet")<BR>RS.Open SQL, yourConnection, adOpenStatic, adLockReadOnly<BR>%><BR><BR>Just to pick one example.<BR><BR>
<BR>Set RsMain = Server.CreateObject("ADODB.Recordset")<BR>RsMain.C ursorType = adOpenDynamic<BR>RsMain.Open <BR><BR>dbConn.BeginTrans<BR><BR><BR>and then a sql statement<BR><BR>it keeps breaking on dbConn.BeginTrans though. why is that?
...dbConn is *ALREADY* in use by another recordset that was opened ForwardOnly. Or at least that's how I read all those MS articles/docs.<BR><BR>Why are you using adOpenDynamic? I can't think of a reasonable real-world use for that from ASP code. (Shouldn't be relevant to this problem; just curious.)<BR><BR>