1. FetchOnDemand not fully implemented - actually reads through all data in
nested datasets and only sends to the client the requested detail dataset -
very inefficient - fatally so - we could deal with this - wrote our own
provider which fixes these issues.
2. We are using nested datasets for master/detail on the client side. The
MIDAS.DLL fails to update the ChangeCount and propagate the change count to
the master datasets, hence you cannot do ApplyChanges as the changeCount on
the master dataset is zero.
3. After a post of a detail dataset when the detail dataset is empty, it
loses the record (it disappears), if you refresh/navigate etc, it reappears
later, it however you add 2 or three records it appears to be quite happy.
4. Because of 2 & 3 it gives Key Violation exceptions, as it appears to lose
the data just keyed. These all seems to be related to the ChangeCount not
incrementing and failure to post records.
Can't do anything about 2,3,4 as they are all problems with midas.dll
<grrrrrrrrrrrr .... ^#%^%$#>
Midas.dll works fine on single level datasets.
Myles.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 21, 2000 5:47 PM
To: Multiple recipients of list delphi
Subject: RE: [DUG]: Problems with CloneCursor
Want to share some of the issues you have had with the clientdataset?
JED
>>Last I heard was that DBExpress was to be based on MIDAS which by the
state
>>of TClientDataSet is anything to go by, it gives me the shivers - I will
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
