Cursor Operation Conflict (no count and aduseclient fixes failed)
- From: "crazyone" <theinsanecoder@xxxxxxxxx>
- Date: 4 Dec 2006 13:46:23 -0800
Hi, i need some help on this, i've got a software to maintain and a
major deployment today has gone catastrophic, i've tried several
solutions so far but nothing seems to do it.
There error we get is Cursor operation Conflict. This error happens
randomly all over the application using ADO in VB6. It never happened
before even when this client was doing large scale testing, but all of
a sudden when going live (much larger scale) this error seems to pop
everywhere...
I've read a lot on this question, tried to turn off the NOCOUNT feature
in the server but it was already off by default, the software
connection string do not specify this therefore is using the default
one. Everywhere i see this error pop i check and the adUseClient is
being used and not adUseServer. I'm really running out of options...
PS : I also checked, we have no triggers in the database that use the
INSTEAD OF structure, just very standard triggers runnning on update or
delete... and there are very few of them in the database.
.
- Follow-Ups:
- Prev by Date: very slow oledb insert to Access - any advice?
- Next by Date: Re: Cursor Operation Conflict (no count and aduseclient fixes failed)
- Previous by thread: very slow oledb insert to Access - any advice?
- Next by thread: Re: Cursor Operation Conflict (no count and aduseclient fixes failed)
- Index(es):