~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From: "Andrew Haslett" <[EMAIL PROTECTED]> Subject: RE: Jet Problem
: How about doing a bit of research first before posting these types of : questions? : : LOL - Sorry, couldn't help myself - never seen you actually ask a question : before :=)) : : I had a quick surf and couldn't find anything either. : : Will test it out myself tonight and see if I can come up with anything. : (Rough punt: wouldn't be anything to do with pooling would it - ie same : connection, same query => cache result.) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ That's one thing that I was looking at: a) tried using an ODBC DSN instead of OLEDB Provider, and made sure "connection pooling" was disabled for the ODBC driver. Didn't help (but it may be possible that the OLEDB Provider for ODBC Drivers is caching it someplace) b) Tried doing: objRS.Open strSQL, strConnect to defeat connection pooling (see http://support.microsoft.com/default.aspx?scid=kb;EN-US;q191572) Didn't change anything... c) The thing that is odd, is if you execute the *same* SQL string twice in a page (eg create two recordsets, even with the same name), you get two different sets of results: <% strSQL = "...." Set objRS = objConn.Execute(strSQL) ' Write out results objRS.Close Set objRS = Nothing Set objRS = objConn.Execute(strSQL) ' Write out results objRS.Close Set objRS = nothing %> However if you refresh the page (even if you make other changes to the page, eg add spurios Response.Writes()), both sets of results stay the same - how on earth does ASP or ADO or OLEBD or Jet know which set of results should be served to which ADO recordset? Cheers Ken --- You are currently subscribed to activeserverpages as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED]
