About the Database Component

[David]

HI All,

   I want to know what the database component you all using.

   When the Database is MSSQL,it will be which one?

   1)uniDBGrid -> DataSource -> dbGo-> SQL Server;

   2)uniDBGrid -> DataSource -> ClientDataSet -> DataSetProvider -> dbGo ->SQL Server;

   3)uniDBGrid -> DataSource -> FireDAC/UniDAC ->SQL Server;

   4)uniDBGrid -> DataSource -> ClientDataSet -> DataSetProvider -> FireDAC/UniDAC ->SQL Server

   When other Databases,which one will be better? Why?

 

   Thank you.

 

   Regards

[David]

Or anybody use another database component?

[zilav]

Standard TADODataSet->dbGo works fine, using it in my unigui projects for 3 years. However I keep all data handling logic in stored procedures, unigui clients don't have a single query SELECT, UPDATE, etc, only EXEC.

Can also recommend EhLib's EhMemTable->EhDataProvider->dbGo if you want more features.

[tappatappa]

ODAC->Oracle DB. We develop using Oracle and Delphi, so Devart ODAC seemed the obvious choice. Is not perfect but is specifically developed for Oracle and uses all the advanced features of the DBMS, plus comes with full sources.

[wangxuebin]

Mysql and mydac

[adragan]

Short answer : All of the above.

I prefer UniDac and I had a good project with Zeos also.

Some problems with dbGo.

[David]

Thanks all.I just want to known which will be better with MSSQL.

[Mediv07]

UniDac --> Oracle, Firebird  works fine.

[David]

Tnanks