Re: MySQL, ADO and ODBC
- From: Brian Bushay TeamB <BBushay@xxxxxxxxx>
- Date: Thu, 28 Apr 2005 20:36:28 -0500
>nope
Then the value of one or more fields in your dataset must be different from the
value in your database. ADO must be able to find the record to update in your
database. The default way of doing this is to use all the field values of the
record from when it was first queried to find a record in the database where the
fields match.
Your ODBC driver must be changing the value of a field.
I have seen this happen with DateTimeFields where miliseconds get truncated but
I don't use MySQL so I don't know if that is your problem
>
>"Brian Bushay TeamB" <BBushay@xxxxxxxxx> wrote in message
>news:04j07114akihihirfbbf8v1d6k43af4do8@xxxxxxxxxx
>> >calls the "post" method , i get an error:
>> >
>> >"Row cannot be located, values have changed since it was last read."
>> >
>> >I'm not using anything like BatchOptimistic, or nothing... its a simple
>> >TADOQuery with the default settings.
>> >
>> > I thought this was related to the MDAC version installed on the system,
>but
>> >i updated in windows 2000 to "MDAC 2.8 RTL" and in WinXP to "MDAC 2.8
>SP1
>> >on Windows XP" but i still get the error. Any ideas? Why does it work
>on
>> >Win2k and not on XP??
>>
>> Does this happen after you have initially inserted the record and then go
>back
>> and edit it before doing a requery?
>> --
>> Brian Bushay (TeamB)
>> Bbushay@xxxxxxxxx
>
--
Brian Bushay (TeamB)
Bbushay@xxxxxxxxx
.
- References:
- MySQL, ADO and ODBC
- From: Emi
- Re: MySQL, ADO and ODBC
- From: Brian Bushay TeamB
- Re: MySQL, ADO and ODBC
- From: Emi
- MySQL, ADO and ODBC
- Prev by Date: MS Access and Delphi?
- Next by Date: Re: stored proc RETURN_VALUE.... there it is, I want to use it !!!
- Previous by thread: Re: MySQL, ADO and ODBC
- Next by thread: ADO and BLOB
- Index(es):
Relevant Pages
|