You can open Microsoft Access databases (.mdb) in Exportizer using these ways:
1. Opening through FD interface. Select FD interface, click Microsoft Access, then fill all needed database parameters.
Example of configuring a database connection:
(required parameters are highlighted)
| Database | C:\db\WorkLog.mdb |
| System database | |
| ReadOnly | False |
| String format | Unicode |
| SQL command separator | ; |
2. Opening through ODBC DSN. Create (if it does not exist yet) an ODBC DSN of the corresponding type using Windows ODBC Data Source Administrator, and point it to your database file. Then select ADO or BDE interface, choose ODBC data source option and then select the needed ODBC DSN from the drop-down list.
3. Opening by specifying file name (interface: ADO). Select File option and then browse for the needed file.
4. Opening through connection string (interface: ADO). Select Connection string option and write a connection string. This way is the most flexible one because it allows to specify many additional parameters in the connection string and override standard Exportizer connection behavior. But it is recommended basically for advanced users. Here are basic connection strings (more examples and details can be found in the Internet):
Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\MyData\MyDatabaseFile.mdb;
DSN=MyAccessDSN;
DSN=MyAccessDSN;PWD=MyPassword;
Provider=MSDASQL.1;Extended Properties="DBQ=c:\MyData\MyDatabaseFile.mdb;Driver={Microsoft Access Driver (*.mdb)};DriverId=25;"
Attention
- This database type is supported only in Exportizer Enterprise and Exportizer Pro (the latter one can open such databases via ODBC only).
- In most cases above, Microsoft Access ODBC Driver is used (explicitly or implicitly). So, it is recommended to have it installed; make sure to install the bit-version of the driver that matches the bit-version of the application (32 or 64).
Notes
- Each Exportizer edition has both 32-bit and 64-bit versions. You can install both and use them depending on what type of database you need to work with.
- You can invoke the ODBC Data Source Administrator directly from Exportizer when it was launched in administrator mode:
See also