Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-08-09 : 08:01:16
|
| darin writes "What does the following error mean : Current Recordset does not support bookmarks. ...I am using code to page through a recordset. If I use the sql code on the asp page it works, but as soon as I slap the code into a Stored Proc, it gives me this error????" |
|
|
simondeutsch
Aged Yak Warrior
547 Posts |
Posted - 2002-08-10 : 23:11:45
|
| If you are using ADO, check what cursortype and locktype you are getting. In your ASP page you might request a bookmarkable cursor, but, when you return data from a stored procedure by using SELECT, I suspect you always get a forward only, read only cursor. Anybody, feel free to check me if I'm wrong on this, bc I'm not sure about it.EDITED: Sorry, this reply might have seemed unclear. Returning a recordset from an SP using an ADO command w/out specifying locktype and cursortype will return forward only/read only. Are you specifying a cursortype?Sarah Berger MCSDEdited by - simondeutsch on 08/10/2002 23:15:34 |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-08-11 : 09:36:24
|
| Changing from a SELECT statement to a stored procedure will automatically choose a non-bookmarkable recordset by default. You should still be able to use a stored procedure, but you would have to explicitly set the ADO cursor type to a setting that supports paging. |
|
|
|
|
|
|
Bookmarks