> 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.
I always wondered why TTable and TQuery weren't abstract and DriverTypes
defined like TBDETable TBDEQuery.
var
t :TTable;
begin
t := TBDETable.Create(self);
...
end;
oh well... My latest excursions into Java have finally shown some decent application
for Interfaces - much better...
--
Aaron Scott-Boddendijk
Jump Productions
(07) 838-3371 Voice
(07) 838-3372 Fax
---------------------------------------------------------------------------
New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
