Components for accessing MS Access databases using DAO (Data Access Objects) and ACEDAO. Uses DAO 3.6, DAO 3.5 and ACEDAO. Be the first to.

See registration database using REGEDIT.EXE program. List of Jet 3.5 ISAM drivers (used by DAO 3.5, DAO 3.51): HKEY_LOCAL_MACHINE SOFTWARE Microsoft Jet 3.5 ISAM Formats List of Jet 4.0 ISAM drivers (used by DAO 3.6): HKEY_LOCAL_MACHINE SOFTWARE Microsoft Jet 4.0 ISAM Formats HKEY_LOCAL_MACHINE SOFTWARE Wow6432Node Microsoft Jet 4.0 ISAM Formats ACEDAO ISAM drivers: HKEY_LOCAL_MACHINE SOFTWARE Microsoft Office 14.0 Access Access Connectivity Engine ISAM Formats HKEY_LOCAL_MACHINE SOFTWARE Microsoft Office 14.0 Access Connectivity Engine. C++ Builder converts DAO interface unit, originally created in Delphi, so return value of Delphi function is converted as the last parameter of C++ function and C++ functions always return HRESULT type. For example CreateDatabase function in declared in Delphi as: function CreateDatabase(const Name: WideString; const Locale: WideString, Option: OleVariant): Database; C++ Builder converts this function to: HRESULT CreateDatabase(const System::WideString Name, const System::WideString Locale, const System::OleVariant Option, _di_Database &CreateDatabase_result); To call this function, you need to add the last parameter: _di_Database db; GetDBEngine()->CreateDatabase('C: database.mdb', dbLangGeneral, EmptyParam, db); All DAO functions (DAO 3.5 interface) are declared in dao.hpp file. Use DML (Data Manipulation Language) SQL statements instead of loops. For example deleting records with SQL statement 'DELETE FROM MyTable' is much faster than deleting each record separately with TDAOTable.Delete statement in loop. Jet database engine contains very sophisticated cost-based query optimizer.

You can activate function ShowPlan to see created plan of execution for each query: Create this key in registry database: MyComputer HKEY_LOCAL_MACHINE SOFTWARE MICROSOFT Jet 3.5 Engines Debug Under this key create a new string value with name JETSHOWPLAN and data ON. You can later turn off this function by setting data to OFF. How do I retrieve table permissions?

I have an application that makes use of various versions of an older COM dll. Some version of the dll use DAO 3.5 to access a Microsoft Access database and some use DAO 3.6 do to the same.

So, my install needs to make sure that DAO 3.5 and 3.6 get installed on the target machine so I can be sure this older COM dll will function, regardless of which version they choose to use. That said, I used to use InstallShield to create installation programs. Installshield has merge modules for just about everything, including DAO 3.5 and 3.6. I am trying to create a setup project in VS 2008 that will do the same. The problem is I cannot find out how to get DAO 3.5 and 3.6 to be included in my setup project. Any ideas on how to do this? Thank you so much!

Thanks for the reply. This article talks about how to include a merge module in a setup project. While this is useful, it isn't any help unless you have the merge module to include. Installsheild comes with a pretty complete library of merge modules to install lots of different Microsoft (and other) technologies.

For example, to include DAO 3.5 and DAO 3.6, all you need to do is select those components from a list of re-distributable modules. All of the details (including the exceptions for different operating systems) are encapsulated within the merge modules.