Each Exportizer edition is available in 32-bit and 64-bit architecture versions.

When choosing which version to download and install please consider the compatibility between Exportizer software and:

Compatibility with OS

You can use Exportizer 32-bit on Windows 32-bit and Windows 64-bit, but Exportizer 64-bit should be used only on Windows 64-bit.

Anyway, on Windows 64-bit, you can install both Exportizer 32-bit and 64-bit on the same computer and switch between them whenever you need. On Windows 64-bit, the Exportizer 64-bit is installed to Program Files folder, and Exportizer 32-bit is installed to Program Files (x86) folder. The application installer knows where to install, so it is recommended not to change the default installation folder.

Compatibility with Other Database Components

Let's explain it with some examples...

If you want to work with dBase (.dbf) files, Exportizer can use different ways to open such files. No matter what way you choose, all involved database components (drivers, OLE DB providers, and Exportizer) have to be of the same bitness, i.e. either all 32-bit or all 64-bit. For example, when you work with those files through the Microsoft dBase ODBC driver, the bitness of Exportizer must match the bitness of the ODBC driver.

Similarly, if you need Exportizer to work with .accdb databases (Microsoft Access 2007 and above), the Exportizer bitness must match the bitness of the ACE OLE DB provider or Access ODBC driver depending on what component (OLE DB or ODBC) you choose when connecting the database from Exportizer.

To work with Oracle, SQL Server, PostgreSQL, Firebird, MySQL, and other server databases, the bitness of Exportizer should be the same as the bitness of the corresponding client; if you plan to work with such databases via ODBC, the bitness of Exportizer should be the same as the bitness of the corresponding ODBC driver.

If you for some reason prefer to work with databases via old BDE, you can do this only in 32-bit version of Exportizer.