• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 426
  • Last Modified:

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?
0
bendecko
Asked:
bendecko
  • 2
  • 2
1 Solution
 
thunderchickenCommented:
You might try

Application.Lock

and

Application.Unlock
 before and after SQL Calls
0
 
bendeckoAuthor Commented:
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
0
 
thunderchickenCommented:
Your right, i was thinking of something totally different.  I thought it had to do with the entire process itself, but it only has to do with application variables...

Have you tried doing something like...

...
cn.open DB_CONNECTIONSTRING
set rs = cn.execute(strSQL)
...
0
 
bendeckoAuthor Commented:
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

0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now