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 architecture (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 architecture of Exportizer must match the architecture of the ODBC driver.

Similarly, if you need Exportizer to work with Microsoft Access 2007+ (.accdb) databases, the Exportizer architecture must match the architecture 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 architecture of Exportizer should be the same as the architecture of the corresponding client; if you plan to work with such databases via ODBC, the architecture of Exportizer should be the same as the architecture 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.

Troubleshooting

What to do if you need to export data from a data source which is available via 32-bit technology, to a target which is available through 64-bit? For example, you need to export data from Excel to Oracle database, but Excel ODBC driver or ACE provider on your computer is 32-bit and Oracle client is 64-bit, or vice versa, etc.

You can use at least two workarounds in Exportizer.

Using Clipboard

First, you export your source dataset to clipboard in Exportizer 32-bit or 64-bit depending on the architecture of the source data provider (ODBC driver, database client etc). Then, in Exportizer of another architecture version, you either export data from clipboard to the target database using Export | Export from Clipboard... menu or open the target database and then import data from clipboard using Import | Import from Clipboard... menu.

If you need to export many datasets at a time, you need to use Exportizer Enterprise and SQL approach (see below).

Using Intermediary SQL Script

This way, you need Exportizer Pro or Exportizer Enterprise.

First, you export your source data to SQL script. Then, in Exportizer of another architecture version, you open and execute the SQL script.

See also