Here you can find the instruction on how to convert data from Paradox tables to Firebird database in Database Tour.

Note: This instruction can be also applied to exporting data to Interbase databases. The export interface is almost identical for Firebird and Interbase on the destination side.

Export Conditions

When converting Paradox data to Firebird, please consider the following:

Note: If your operating system is 64-bit, you can install both Database Tour 32-bit and Database Tour 64-bit and use them independently.

Configuring Paradox to Firebird Exporting

  1. Launch Database Tour.
  2. Register your source Paradox database. It must be a folder where the source Paradox (*.db) files are located.
  3. Register your target Firebird database. The recommended interface is FD, but other options are also available. If the target database does not exist yet, create a target Firebird file. Note: You can create and/or register the target database from the Export dialog during the exporting.

Export Steps

Exporting a Dataset

  1. Open the registered Paradox database.
  2. Choose a dataset to export. I.e. select a table in the table list or write and execute your database query.
  3. If you chose the table, switch to Data page.
  4. Click Export button in the toolbar above.
  5. Switch to the Database tab and select your registered Firebird database as the target database.
  6. Specify a target table. Turn on all Memory saving mode options. If source data and/or column names on any side may contain Unicode characters, make sure to choose the correct SQL stream encoding, e.g. UTF-8. Choose the correct Export mode. Exporting data to Interbase or Firebird
  7. Click Next. Check the source-to-target field mappings. Here, you can remove unnecessary mappings, add calculated fields, specify target column types (when exporting to a new table) etc.
  8. Click Export.

Exporting Multiple Datasets

  1. Open the registered Paradox database.
  2. You can export either selected tables or open datasets of any kind.
    • Exporting selected tables
      1. Switch to the Tables tab to the left.
      2. Right-click the table list and choose Multiple Selection.
      3. Select tables to export.
      4. Click Export button or choose Tools | Export Data | Selected Tables... menu.
    • Exporting open datasets (you can use SQL queries results or a mix of queries and tables)
      1. Open multiple SQL windows, type SQL queries there and execute them. Open needed tables too.
      2. Choose Tools | Export Data | Open Datasets... menu.
      3. Choose the datasets to export and click OK.
  3. Switch to the Database tab and select your registered Firebird database as the target database.
  4. Turn on Memory saving mode options. If source data and/or column names on any side may contain Unicode characters, make sure to choose the correct SQL stream encoding, e.g. UTF-8. Choose the correct Export mode. Leave the field for target table name blank.
  5. Click Next. Specify the source-to-target table mappings. Here, you can specify target table name for each source table and nested field mappings for every table pair.
  6. Click Export.

Exporting Paradox to Firebird from Command Line

Here are some examples of exporting Paradox data to Firebird database using Database Tour command line. Each command line below can be easily transformed to an action file, which can be used instead of the command line. We recommend to use action files whenever possible because they are easier to maintain and are more comfortable to work with.

Note: The command line functionality is available in Database Tour Pro.

Exporting an Paradox Table to Existing Firebird Database

A command line to export a table from a Paradox file to existing Firebird database:

"C:\Program Files (x86)\Vitaliy Levchenko\Database Tour Pro 10\dbtour.exe" /export /ExportType=DATABASE /ExportMode=REPLACE+INSERT /IncludeMemo /SrcDBInterface=ado /SrcDBKind=FILE /SrcDBDriver=Paradox /SrcDB=C:\MyDatabases /SrcTableName=salary /TrgDBInterface=fd /TrgDBKind=FILE /TrgDBDriver=Firebird /TrgDB=C:\MyDatabases\employee.fdb /TrgTableName=SALARY

Notes

Exporting in Silent Mode

Let's improve the above example by allowing it to run in silent mode, when no windows are shown. In this mode, it is recommended to add a log file to control the exporting process:

"C:\Program Files (x86)\Vitaliy Levchenko\Database Tour Pro 10\dbtour.exe" /silent /export /ExportType=DATABASE /ExportMode=REPLACE+INSERT /IncludeMemo /SrcDBInterface=ado /SrcDBKind=FILE /SrcDBDriver=Paradox /SrcDB=C:\MyDatabases /SrcTableName=salary /TrgDBInterface=fd /TrgDBKind=FILE /TrgDBDriver=Firebird /TrgDB=C:\MyDatabases\employee.fdb /TrgTableName=SALARY /LogFile=C:\MyDatabases\export.log

Exporting All Paradox Tables from a Folder

Exporting all Paradox files from a folder to existing Firebird database in silent mode:

"C:\Program Files (x86)\Vitaliy Levchenko\Database Tour Pro 10\dbtour.exe" /silent /export /ExportType=DATABASE /ExportMode=REPLACE+INSERT /IncludeMemo /SrcDBInterface=ado /SrcDBKind=FILE /SrcDBDriver=Paradox /SrcDB=C:\MyDatabases /SrcTableName=* /TrgDBInterface=fd /TrgDBKind=FILE /TrgDBDriver=Firebird /TrgDB=C:\MyDatabases\employee.fdb /TrgTableName=* /LogFile=C:\MyDatabases\export.log

Note: In the example above, target table names and their column names will be the same as in the source tables. If you want to override this behavior, you should create a table mappings file, and then add it to the command line:
"/TableMappingsFile=C:\MyDatabases\Export\Paradox-To-Firebird-Table-Mappings.xml"
You can create such a file from Export window when exporting multiple tables.

Alternative Scenario Using Generated SQL Statements

If you for some reason could not export data directly from Paradox file to Firebird, Database Tour can export the Paradox data to a SQL script first, and then load data into Firebird database using Database Tour or any other SQL tool. You can export data to SQL script either by GUI or from the command line.

But please note, that when choosing exporting to SQL script, your export process will have two phases: first, exporting the data from the source database to SQL script; second, loading data from the script to your target database. So, this way can be less effective, especially for large datasets or when automating the data exporting.

Anyway, we recommend to try both scenarios and select the fastest and/or the most convenient one.

Reusing Export Configuration

Before closing the Export window, you might want to save your export configuration for future use.

Saving and Loading Field or Table Mappings

Sometimes, you need to reuse your changed field or table mappings, for example. For example, you overrode the default field mapping (i.e. deleted some fields, added calculated fields, changed the target field names etc), and want to save your work. You can save the field/table mappings to a file by clicking Save button (above the mapping grid). Next time, when exporting the same or similar table, you can load the mappings from that file by clicking Load button.

The created field mappings file or table mappings file can also be used in building your command line when automating the exporting process.

Saving and Loading Export Definitions

You can save all export definitions (including field/table mappings and other selected options) by choosing Tools | Save Export Definitions.... To load the definitions from file, choose Tools | Load Export Definitions.... Such a practice can save your time and guaranties that specified combination of options will be exactly reproduced.

Saving export definitions

See also

Opening Paradox Files

Opening Firebird Databases

Exporting Data

Database Export Format

Command Line Usage: Export / Import Data

Action File

Field Mappings File

Table Mappings File