🚀 go-pugleaf

What I do is use a seperste TADOCommand object with an UPDATE statement to
write.  You still need to Requery/Refresh/Reopen your dataset to see the
changes, but you can write whatever you want whenever you want.  The problem
has to do with ADO/Jet using the entire record for updates.  This could also
happen if you changed a fields in the Primary Key.

Mark



"Juan Jos� S�nchez" <JUANJOSE94@terra.es> wrote in message
news:3abfffb9_2@dnews...
> Hi all!
>
> I've tried to write two clients that access the same database (MS Access
> 2000) via OLEDB driver for Microsoft Jet 4.0, the problem is that the
> EOLEException ( ' The especified row could not be located for
updating.Some
> values may hace been changed since it was last read ' ) occured when each
> application tried to write different data in the same record NOT
> SIMULTANEOUSLY.
> Here are the main code of both clients:
>
> Client 1
> ...
> void __fastcall TForm1::Button1Click(TObject *Sender)
> {
>     ADODataSet1->Refresh();
>     ADODataSet1->Edit();
>     ADODataSet1->FieldValues["FIELD1"] = 1;
>     ADODataSet1->Post();
> }
>
> Client 2
> ...
> void __fastcall TForm2::Button1Click(TObject *Sender)
> {
>     ADODataSet1->Refresh();
>     ADODataSet1->Edit();
>     ADODataSet1->FieldValues["FIELD1"] = 2;
>     ADODataSet1->Post();
> }
>
> How can any clients write data to the same database correctly? Should I
consider some settings to my ADOConnection that I have ignored?
>
> Note: When only one client writes to the database and the other reads
there wasn't any problem.
>
> Thanks all
>
>
>