eva/3 Application BuilderAccess® Migrator 

Conversion process

Before starting the conversion please take shure that the Microsoft® Access® database is not opened by a Microsoft® Access® instance and isn't be protected by a password. Additional all starting processes within the Microsoft® Access® database should be deactivated because teh database will be opened by another Microsoft® Access® instance for the conversion process.

1. Starting the conversion

The conversion process can be started using the Eclipse menu entry File > Export. Afterwards the conversion dialog appears. (s. fig. 358 ).

Fig. 358: Starting the conversion process
Fig. 358: Starting the conversion process

In the conversion dialog, the entry eva/3 Access Import is to be selected and confirmed by pressing the Next button. Now the attributes for the conversion process can be adjusted. (s. fig. 359 ).

2. Conversion set up

Fig. 359: Starting the conversion process
Fig. 359: Starting the conversion process

First, the target project and the Microsoft® Access® mdb file should be selected. If there isn't already a target project, a new project can be created using the button New Project (see capture 2.1).

If only parts of the Microsoft® Access® database to be converted, the undesired parts can be choosen by deselecting the corresponding check box.

Hint: If parts of a Microsoft® Access® database are not converted, all reffering attributes are not converted, too. For example formas and reports won't be connected to a table if the attribute Import Tables was deselected.

The check box Convert data to target database allows the migration of all data from the Microsoft® Access® database into a new database system. If this check box are disabled, the original Microsoft® Access® database will be used as data source. Activating the check box releases the Next button for entering the connection data for the target database (see capture 2.2).

By activating the button Finish the conversion process starts. If the converion is startet the first time, a dialog prompts for installing the system file jacob.dll. This file is for remote controlling the Microsoft® Access® instance which is needed for the conversion process. The jacob.dll will be copied into the bin folder of the currently used java installation.

2.1 Creating a new project

The eva/3 project creation dialog (see fid. 268) allows to create a new, empty eva/3 project.

Fig. 360: Neues Projekt anlegen
Fig. 360: Neues Projekt anlegen

First the desired project name for the new project should be enterted into the field Project name. Additional it is recommendable activating the check box Create separate source folder for manage all java source codes in a separate folder.

2.2 Set up the target database

During the conversion process, all data from the source Microsoft® Access® database can be migrated to a new taget database. The migration process need some connection data for the target database which can be entered into the connection dialog. (see fig. 269). Additional information for setting up a connection please take a look at Create Database Connection.

The conversion process will be started by activating the Finish button.

Fig. 361: Create Database Connection
Fig. 361: Create Database Connection

3. The conversion process

Dependent on the Microsoft® Access® database size the conversion process can take a lot of time. if the attribute Convert data to target database was activated all data will be copied to the target database. This can take a lot of time, too.