Thank you for your interest in Direct Access Components for MySQL!

DAC for MySQL: "What?" and "Why?"

DAC for MySQL is a member of microOLAP Direct Access Components line of products.

Our DAC products allow to create Borland Delphi/C++Builder applications with the direct access to SQL servers without BDE and ODBC.

All these products were developed according to the following requirements:

1. Avoid the weaknesses of BDE/ODBC technology:

Deployment:

You add to your distributive more than 5Mb with BDE;

If another BDE-based program will be installed on user's workstation it can conflict with your application;

ODBC profile on user's workstation can be changed or damaged;

Possible ODBC drivers conflicts.

Performance:

BDE uses another layer of middleware (ODBC). So, in this case you have two resource eaters: BDE and ODBC.

BLOB fields:

Several of the SQL Links drivers provided with Delphi Enterprise Edition do not work with BLOB data types correctly;

Data access:

BDE cannot access some RDBMS data types at all;

Cost:

Only the Enterprise Edition of Delphi (~$3000) includes the BDE SQL Links required for connecting to DB servers.

DAC: Ability to work with Professional Edition.

2. Keep migration of old BDE/ODBC based projects to DAC easy:

No additional knowledge required:

DAC components are TDataSet compatible. Implementing of additional RDBMS-specific functions and properties must be obvious;

No external modules:

DAC for MySQL does not require any additional external modules from MySQL (even libmysql.dll).