Compile Migration Objects

If you modify your migration objects, you must compile them in the following order:

1. MigUtil

2. MigrationModifyObj

3. MigrationLogObj

4. MigrationReadObj

5. MigrationWriteObj

6. MigrationMainObj

Note the following dependencies, and the resulting consequences for compilation order:

• MigrationMainObj depends on the other four modules.

• MigrationReadObj depends on MigUtil and MigrationModifyObj.

• MigrationWriteObj depends on MigUtil and MigrationLogObj.

• MigrationLogObj depends on MigUtil.

• MigrationModifyObj depends on MigUtil.

The MigrationLogObj object is used by the MigrationWriteObj and MigrationMainObj objects to log errors.

The MigrationReadObj object does not log errors directly because any error it returns are logged from the MigrationMainObj object.

If the MigrationWriteObj object encounters errors while writing, it rolls back the entire user record, and then returns an error back to the MigrationMainObj object. Then the MigrationMainObj object logs the error. The MigrationWriteObj will only use the MigrationLogObj directly when errors occur in the roll back process itself.

If you make modifications to the code, recompile using Microsoft Visual Basic 6.0 Service Pack 3 or Microsoft Visual C++ 6.0 Service Pack 3.

The following table shows the required compiler settings for each component.

All rights reserved.