getting RecordCount = -1

[Ankur Bakliwal]

Hello Friends, I have a problem with recordsets. I m getting Rs.RecordCount = -1 while calling a store procedures here is code - Set cmd = Server.CreateObject("ADODB.Command") Set rs = Server.CreateObject("ADODB.RecordSet") cmd.ActiveConnection = myCon cmd.CommandText = "SP_Name" cmd.CommandType = 4 cmd.CommandTimeout = 300 cmd.Parameters.Append cmd.CreateParameter("@par1",20,1,10,1) cmd.Parameters.Append cmd.CreateParameter("@par2",20,1,10,1) cmd.Parameters.Append cmd.CreateParameter("@par3",20,1,10,20) cmd.Parameters.Append cmd.CreateParameter("@par4",20,1,10,Null) Rs.CursorLocation = 3 Rs.LockType = 1 Rs.CursorType = 3 Set Rs = cmd.Execute Response.Write "
RecordCount = " & Rs.RecordCount pls give some usefull solution. Thanks, Ankur Bakliwal

[Christian Graus]

What happens if you take those parameters, and call the stored proc within SQL Server ?

Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )

[Ankur Bakliwal]

In Sql Server with same parameter that SP gives me 2 records as result.

Thanks, Ankur Bakliwal

[Christian Graus]

Then there must be a problem with the code. Not sure what, without seeing the proc.

Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )

[roel_v]

I found this on MSDN: The cursor type of the Recordset object affects whether the number of records can be determined. The RecordCount property will return -1 for a forward-only cursor; the actual count for a static or keyset cursor; and either -1 or the actual count for a dynamic cursor, depending on the data source. You are using CursorType = 3, which corresponds to a static cursor, so it should return. However, it also says: The property returns -1 when ADO cannot determine the number of records or if the provider or cursor type does not support RecordCount. What provider are you using? In general, the safest solution is to just include a count(*) in your stored procedure and return that as an output parameter. Let me know if this works for you. Roel