bendecko
asked on
Recordset Cursor Operation Conflict
Hi
I've got a site where I have quite a few DB access commands. Most commonly they are in the form:
objRecordset.Open strSQL, DB_CONNECTIONSTRING, adOpenKeyset, adLockPessimistic, adCmdText
I've been occasionally getting 'Recordset Cursor Operation Conflict asp errors' Is this due to the adLockPessimistic parameter and the number of users in the system increasing?
Any suggustions?
I've got a site where I have quite a few DB access commands. Most commonly they are in the form:
objRecordset.Open strSQL, DB_CONNECTIONSTRING, adOpenKeyset, adLockPessimistic, adCmdText
I've been occasionally getting 'Recordset Cursor Operation Conflict asp errors' Is this due to the adLockPessimistic parameter and the number of users in the system increasing?
Any suggustions?
ASKER
Recordset Cursor Operation Conflict errors could be due to pessmistic locking?
What does the application lock actually do? What happens if two processes try to lock a table at the same time - wouldn't i get the same problem?
Bendecko
What does the application lock actually do? What happens if two processes try to lock a table at the same time - wouldn't i get the same problem?
Bendecko
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Having a bit of a clean up of <unlocked questions>
This would almost certainly work I now know to use the connection object for INSERTS and UPDATES and leave the recordset for SELECTS
thanks
This would almost certainly work I now know to use the connection object for INSERTS and UPDATES and leave the recordset for SELECTS
thanks
Application.Lock
and
Application.Unlock
before and after SQL Calls