I'm having an issue with returning the recordset back from a stored procedure. I'm using an MTS component (VB), using ADORecordset 2.6 Library, to run a stored procedure in MS SQL Server 7.0. The Recordcount always returns as -1 and the the movelast method fails with error
"Rowset does not support fetching backward." Below is a portion of the VB code. The Stored Procedured does contain the SET NOCOUNT ON statement.


Set conn = New ADODB.Connection
20 conn.ConnectionTimeout = 90
30 conn.CommandTimeout = 60


'Open the connection
40 conn.Open ConnectionString

50 Set rs = New ADODB.Recordset

60 rs.CacheSize = PageSize
70 rs.PageSize = PageSize
80 rs.CursorLocation = adUseServer
90 rs.CursorType = adOpenStatic
100 rs.LockType = adLockReadOnly
110 Set rs.ActiveConnection = conn

120 rs.Open SQLStr

I found the following two kB articles, but neither explains how to solve the problem. Any experience or ideas with this?

http://support.microsoft.com/default...b;en-us;306388
http://support.microsoft.com/default...b;en-us;194973

Try specifying that it is a stored-procedure like this:

It doesn't surprise me that a stored procedure would not support "moving backward."

It looks like all the settings are correct.

The data source (Table or stored procedure) has nothing to do with the recordset movement. Naturally, a stored procedure will not allow edits of the underlying data, but a static recordset should allow movement in both directions.

You will always get a record count = -1 when the cursorlocation is adUseServer.