MYSQL solution for "Row cannot be located, values have changed since it was last read."
- From: "marcel" <marcel63@xxxxxxxxxxx>
- Date: 30 Aug 2005 02:06:57 -0700
Dear ADO friends,
I think I solved part of this problem using:
- MYSQL 4.1
- MYSQL ODBC driver 3.51
- DELPHI 7.0 with 7.1 update
- MDAC 2.8 SP 1
- WINDOWS XP
I had a very simple table with a auto incrementing primary key. When I
did a edit-> post on the table where nothing changed and I put one
integer field equal to the original value I got the above error.
thus with original value
mytablefield.value = 1;
mytable.edit
mytablefield.value := 1;
mytable.post
gives error..........
and
mytable.edit
mytablefield.value := 0;
mytable.post
does not (the same happened if I used a TDBGRID with navigator)
Thus I tried all kind of stuff that I found on this newsgroup. Nothing
helped. Also the TbetterADO did not.
Finally I found a remark on the mysql reference manual:
"For all versions of Access, you should enable the MyODBC Return
matching rows option"
and thus I did and it worked and the sun began shining again, angels
cheering etc.
Thus for windows xp. Open your "ODBC data source administrator" and
"Configure" your MYSQL datasource. Under the "Advanced" -> "Flags1" TAB
make sure "return matching rows" is checked !!
good luck !
.
- Prev by Date: Re: Question about not required fields
- Next by Date: Re: DBF WITH EXTENSION OTHER THAN .DBF ( I.E. DAT )
- Previous by thread: Question about not required fields
- Next by thread: 'Insufficient info' to refresh detail tables
- Index(es):
Relevant Pages
|