Thanks for the replies.
Bypassing the BDE is not an objective in itself. By "Thin" I am referring
to designing applications in such a way as to minimise the network traffic,
the objective being to make the app run as fast as poss over a narrow pipe.
(56K Modem) Take a look at a telnet session into an AS400 as an example of
"Thin" within this definition. I am not a three tier expert, but I find it
hard to beleive that a three tiered object brokering approach can be an
efficient model for slow networks, although there are other advantages in
usnig DCom Corba etc.. It seems to me that using optimised data access
components like FIB and the Oracle equivilent (I never can remember the
correct order of the Acronym for the oracle components) would offer the
thinest approach possible..
So, does DAO fall within the scope of my goal? or does it drag objects
accross the network also.
Thanks,
Tony.
-----Original Message-----
From: Nic Wise <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Date: Thursday, 2 September 1999 5:19 PM
Subject: Re: [DUG]: Thin Database Components.
> So if something is OLE DB capable then it is apparently a short step from
there
> to ADO which of course means the BDE is bypassed.
>
OLE DB = driver for ADO.
ADO-MD = multi dimensional ADO, ie OLAP, which is rather cool...
N
--
Nic Wise - +64.21.676.418 - +64.9.277.5309 - [EMAIL PROTECTED]
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
