September 8, 2004 at 11:26 am
We recently applied SP3a.
We now get an "unspecified error" on any proc that uses FETCH ABSOLUTE to return a result set but only when creating an ADO recordset. The queries run fine in QA.
Also, if the FETCH statement fetches values into local variables things are fine.
For example:
"FETCH ABSOLUTE @Row FROM SomeCursor INTO @SomeVariable" works fine.
"FETCH ABSOLUTE @Row FROM SomeCursor" will error
I rolled back the MDAC installation to 2.6xxx and it works fine.
I also tried installing MDAC 2.8 to no avail.
Has anyone seen anything like this? I've searched here, MS SQL Server forums, Google, everywhere I can think of and not seen one reference to a similar problem.
Any clues/advise would be appreciated.
Also, here is the data access code:
Dim cnConnection As ADODB.Connection
Dim rsRecords As ADODB.Recordset
Set cnConnection = CreateObject("ADODB.Connection")
cnConnection.Open strConnection
Set rsRecords = CreateObject("ADODB.Recordset")
rsRecords.ActiveConnection = cnConnection
rsRecords.CursorLocation = adUseClient
rsRecords.CursorType = adOpenStatic
rsRecords.Open strQuery, , , , QO_UseUnknown <----This line errors
Eric Carlson
September 9, 2004 at 4:50 am
I'd seriously advise staying away from cursors...the performance is (99.99% of the time) VERY poor compared to SET-BASED processing.
post the actual SQL query.....a beneficial rewrite might solve more problems than you currently know.
September 9, 2004 at 6:20 am
Thanks for the reply. I am aware of cursor performance issues. Just trying to avoid a rewrite at the moment.
We did discover that this issue does not happen on Win2K or presumable anything above. Our server is still NT, anxiously awaiting an upgrade. Just wanted to post this in case anyone else ran into the same issue. Looks like we'll have to rewrite anyway!
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply