We're getting "Cursor conflict error" when merely trying to run the UPDATE method against an ADO Forward-Only cursor. This was working last week (and should) but now it's blowing up. We installed a new security hot fix for SQL Server last week. The error still occurs even after rolling the patch back. Here's code:
[tt]'---------------------------------------------------------------------------------------
Function GetNewID
Dim rsID
set rsID=Server.CreateObject("ADODB.Recordset"
rsID.ActiveConnection=connectionString
rsID.Source = "SELECT GLOBAL_ID FROM GLOBALS WHERE ID=1"
rsID.CursorType = 1
rsID.CursorLocation = 2
rsID.LockType = 3
rsID.Open
GetNewID = rsID.Fields("GLOBAL_ID"
.Value + 1
rsID.Fields("GLOBAL_ID"
.Value = GetNewID
rsID.Update
rsID.Close
Set rsID = Nothing
End Function[/tt]
Thanks in advance!
[tt]'---------------------------------------------------------------------------------------
Function GetNewID
Dim rsID
set rsID=Server.CreateObject("ADODB.Recordset"
rsID.ActiveConnection=connectionString
rsID.Source = "SELECT GLOBAL_ID FROM GLOBALS WHERE ID=1"
rsID.CursorType = 1
rsID.CursorLocation = 2
rsID.LockType = 3
rsID.Open
GetNewID = rsID.Fields("GLOBAL_ID"
rsID.Fields("GLOBAL_ID"
rsID.Update
rsID.Close
Set rsID = Nothing
End Function[/tt]
Thanks in advance!