TDataset - probably. TBDEDataset - no. Instead (I presume) a TDataset
descendant that uses dbClient calls rather than BDE calls to drive it, and
(more) new components to replace TQuery and TTable that descend from it.
I'm also assuming that all the buffering that the BDE did will now be up to
the application, hence the integration with MIDAS.
If I understand correctly, to a large degree you'll be implementing the
BDE's functionality yourself, but in any way you choose. It will mean more
work but fewer constraints, cross platform support if you stick with CLX,
and probably better database performance in the long run. But that last bit
is up to you.
Cheers,
Carl
-----Original Message-----
From: Mark Derricutt [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 6 July 2000 11:15 AM
To: Multiple recipients of list database
Subject: RE: [DUG-DB]: BDE RIP
On Thu, 6 Jul 2000, Nic Wise wrote:
> No, you _had_ the bde, you now have dbCLX. Except I'd imagine the BDE
would
> still be there for legacy reasons, just not in Kylix.
Does dbCLX still use the familier TDataSet style components?
--
Inspired by the taste of horror, proud to be insane forever
Let out the killer in me! (c) Dismal Euphony
Now Playing: Leopoldo Innecco & Emir Isilay - Planet Funk - Winamp
---------------------------------------------------------------------------
New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
