1. Opening through FD interface. Select FD interface, click Microsoft Access, then fill all needed database parameters.

2. Opening through ODBC DSN (interface: ADO or BDE). Select ODBC data source option and then select the ODBC DSN from the drop-down list. But first, you should create an ODBC DSN of the corresponding type using Windows administrative tools, and point it to the database file.

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;"

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).
This database type is supported only in Exportizer Enterprise. Exportizer Pro can open such databases via ODBC only.

See also

 Connection Strings Examples