ADO might be thin but thats only because it sits on top of a big pile of
... ODBC, RDS, DAO, MDAC and whatever else MS are calling there
database access (no pun intended) 'stuff' today.
People complaining about the size of the BDE (ie me), should try and
compare with the size of the MS DB access layer - only difference is
that the MS stuff comes buried among 100Mb+ of other stuff.
That being said, dropping the BDE and moving to something like Adonis or
ODBCExpress will obviously reduce the deployment size of the client app.
Grant Black
Software Developer
SmartMove (NZ) Ltd
Phone: +64 9 361-0219 extn 719
Fax : +64 9 361-0211
Email: [EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 22, 1999 10:52 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [DUG]: How thin the client will be?
>
> How about using COM/ADO? This assumes ADO is installed on your clients
> - it's a lot smaller than the BDE - but I think it uses ODBC??
>
> If you are using Delphi 4 - Check the Delphi Direct - Tech Voyage -
> there is an entry there for using Delphi and ADO.
>
> Myles.
>
> -----Original Message-----
> From: Yanbo Li [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, April 22, 1999 10:20 AM
> To: Multiple recipients of list delphi
> Subject: RE: [DUG]: How thin the client will be?
>
> I appreciate your idea, not because I am conservative, but I
> MUST make
> the app very thin. BDE is absolutely unacceptable to install in
> potential 15k clients. If anyone has the experience to program a
> driver
> that links to Oracle, I am very glad to ask my boss to pay the
> above
> average rate. I only need very simple functions like ExexSQL,
> GetQueryRlt.
>
> Also thank all who respond my silly question.
> I am happy that I can learn in DUG.
>
> Cheers
> Yanbo
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Eliot Muir
> Sent: Wednesday, April 21, 1999 11:23 PM
> To: Multiple recipients of list delphi
> Subject: Re: [DUG]: How thin the client
> will be?
>
> Call me a conservative....but why bother with
> all these
> proprietary networking stuff? Bound data type controls are
> renowned for
> making unscalable applications - the little bit of time saved in
> throwing apps together is usually absorbed in the maintenance
> and slow
> performance that these complicated technologies result in -
> especially
> when they don't work.
> DCOM and CORBA etc. don't achieve what they are
> supposed
> to - which is transparent operation of applications over
> networks. I
> haven't used MIDAS to be honest but I bet it's not the magic
> panacea
> that the spec sheet describes.
> The best approach is also the simplest.
> Implement your
> own simple client-server library based on on straight TCP/IP or
> maybe
> RPC, stream over some type of hash table object with a version
> numbering
> scheme, and get your server to decipher the calls and talk to
> the
> database.
> The advantages are that it's transparent - you
> know
> exactly when and what data
> is being
> sent across the network. It's easy to debug,
> you have
> complete control so it's
> easy to optimise
> * you don't have to spend heaps of time evaluating crap
> third
> party products which don't work.
> And lastly no license fees or danger of your
> client-server architecture becoming obsolete if the product you
> used
> gets dumped or the company which makes it goes under.
>
>
>
> ----------------------------------------------------------------------
> -----
> 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
