ADO is fine if speed is not an issued..
i.e.
Oracle table with child table ADO Components 5 seconds per
scroll
MSSQL speed not as noticable
MySQL Buggy (more cos of the ODBC Drivers
etc)
Postgres as with MySQL
Also for installation of the application on the client
machines, With ADO the ODBC Drivers need to be installed also (and
sometimes the DSN) although it is my practice to use DSNless
connections,
Whilst with the DBXpress or SQLDirect type components no
installation is required on the users machines, This is prevelent in my
work environment WAN where my Application (plus very small dll's) are
distributed to each server to the same directory, anyone in the company from any
office (regular or visiting) can open the application and use it immediately..
(Centralised Database)
Yes third pary components I generally say NO WAY!!! however
these tools/drivers are for both C#, and Delphi languages and the company's
selling them seem to want to keep it compatible with the changes
in Delphi.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Coulter
Sent: Monday, 11 October 2004 3:58 p.m.
To: [EMAIL PROTECTED]
Subject: [DUG] ADO or SQLDirect ?
Hi
All.
I am
just doing a bit of an investigation at the moment, and wonders what others had
found was best to talk to an MSSQL server with Delphi.
Do
you use ADO? or do use controls that talk to the MSSQL API like SQLDirect
?
Thanks,
jeremy
_______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
