Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Rowset position cannot be restarted?

LEGEND ,
Oct 11, 2007 Oct 11, 2007
Microsoft OLE DB Provider for SQL Server error '80040e18'

Rowset position cannot be restarted.

/pagename.asp, line 408

I am using asp, stored procedure and i get the above error. Any ideas
how to fix it?
TOPICS
Server side applications
2.7K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Oct 11, 2007 Oct 11, 2007
Art wrote:
> Microsoft OLE DB Provider for SQL Server error '80040e18'
>
> Rowset position cannot be restarted.
>
> /pagename.asp, line 408
>
> I am using asp, stored procedure and i get the above error. Any ideas
> how to fix it?

On line 408 sits:

-----------------------

rsName.MoveFirst()
-----------------------


-----------------------------Stored Procedure

<%

set commSearch = Server.CreateObject("ADODB.Command")
commName.ActiveConnection = MM_connShnta_STRING
commName.CommandText = "storeprocedurename"
commName.Parameters.Append commSearch.CreateParameter("@RETURN_VALUE", 3, 4)
commName.Parameters.Append commName.CreateParameter("@search1", 200,
1,100,commName__search1)
commName.Parameters.Append commName.CreateParameter("@search2", 200,
1,20,commSearch__search2)
commName.Parameters.Append commName.CreateParameter("@search3", 200,
1,6000,commSearch__search3)
commName.CommandType = 4
commName.CommandTimeout = 0
commName.Prepared = false
set rsName = commName.Execute
rsName_numRows = 0

%>
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Oct 15, 2007 Oct 15, 2007
Any ideas what is wrong? I've tried doing a google to find out what is
causing this but I found a number of instances of people running into
the same problem but no solutions.
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Oct 15, 2007 Oct 15, 2007

How do you change "cursor" location from server to client?
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Oct 15, 2007 Oct 15, 2007
"Art" <lee_nospam_@nospam_artjunky.com> wrote in message
news:fevrc8$2qo$1@forums.macromedia.com...
>
> How do you change "cursor" location from server to client?

this thread gives some details about the reasons why this is happening
< http://groups.google.com/group/macromedia.ultradev/browse_thread/thread/fe8c4acb6ede7a9a/7c250437cd7...

In Dreamweaver MX you can change the cursor location by selecting the
recordset from the serverbehaviors panel, that should activate the Recordset
Inspector in the Properties Panel, select Client from the Cursor location
Drop down.

Joris




Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Oct 16, 2007 Oct 16, 2007
LATEST
Joris van Lier wrote:
> "Art" <lee_nospam_@nospam_artjunky.com> wrote in message
> news:fevrc8$2qo$1@forums.macromedia.com...
>>
>> How do you change "cursor" location from server to client?
>
> this thread gives some details about the reasons why this is happening
> < http://groups.google.com/group/macromedia.ultradev/browse_thread/thread/fe8c4acb6ede7a9a/7c250437cd7...
>
>
> In Dreamweaver MX you can change the cursor location by selecting the
> recordset from the serverbehaviors panel, that should activate the
> Recordset Inspector in the Properties Panel, select Client from the
> Cursor location Drop down.
>
> Joris
>

Thanks but I am using CS3 and changing the cursor location is no longer
an option unless you hand-code it as I did.

The solution was to add the 3rd line in. This changes the cursor to
client side. Don't totally understand it but it worked.

set commSearchResults = Server.CreateObject("ADODB.Command")
commName.ActiveConnection = MM_connStringname_STRING
--->commName.ActiveConnection.CursorLocation = 3 ' adUseClient
commName.CommandText = "results"

Thanks for your help.



Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines