Re: Row cannot be located for updating. Some values may have been changed since it was last read
- From: "Christian Dubois" <cdubois@xxxxxxxxxxx>
- Date: Wed, 26 Apr 2006 12:29:30 -0400
Yes I try the Kevin's suggestion and I still have the problem.
The reason of my problem, I think, is because, in my view, I made a SUM on a
float field. If a cast in integer the result of the sum, I don't get the
error.
What I really want to do is to force my dataset to only use "Key fields"
when they internally buid the update query. Actually, it use all the
modified fields. But the property available to do this (Update Criteria) is
not working...
Am I in a dead end?
"Guillem" <guillemvicens-nospam@xxxxxxxxxxxxxxxxxx> wrote in message
news:xn0elfvez7zqmd000@xxxxxxxxxxxxxxxxxxxxxxxxx
Christian Dubois wrote:
I am using a client-side cursors and I cannot use a server side
cursor. I understand that ADO match the "before edit field values"
before updating the database. Is it the reason why I change my
dataset's properties ['Update Criteria'] to adCriteriaKey : so the
database will only match the primary key instead of all modified
columns (adCriteriaUpdCols). But I still get the error message even
if I change this property, so I don't understand what's happenning.
Christian
sorry, should have been a little more specific. That post only explains
why it happens. The solution to your problem can depend on exactly what
you are doing. Of course, switching to server side cursors is one,
although not necessary the only one. Have you tried Kevin's suggestion?
--
Best regards :)
Guillem Vicens Meier
Dep. Informatica Green Service S.A.
www.clubgreenoasis.com
--
Contribute to the Indy Docs project: http://docs.indyproject.org
--
In order to contact me remove the -nospam
.
- Follow-Ups:
- References:
- Row cannot be located for updating. Some values may have been changed since it was last read
- From: Christian Dubois
- Re: Row cannot be located for updating. Some values may have been changed since it was last read
- From: Guillem
- Re: Row cannot be located for updating. Some values may have been changed since it was last read
- From: Christian Dubois
- Re: Row cannot be located for updating. Some values may have been changed since it was last read
- From: Guillem
- Row cannot be located for updating. Some values may have been changed since it was last read
- Prev by Date: Re: connect to sql server with program pass userid and password
- Next by Date: Re: Row cannot be located for updating. Some values may have been changed since it was last read
- Previous by thread: Re: Row cannot be located for updating. Some values may have been changed since it was last read
- Next by thread: Re: Row cannot be located for updating. Some values may have been changed since it was last read
- Index(es):
Relevant Pages
|