Upgrading teamwork MDACs

Introduction

Some teamwork MDACs versions are not compatible (for example, the 4.2.d and 4.3 versions must not be used on the same repository).

Version 4.3 or later of the teamwork MDACs are now able to detect version conflicts between the MDAC used to create the repository and the MDAC selected in the project.

In the case of a version conflict, no teamwork commands can be run by regular users. The repository administrator is instead given the possibility of migrating the repository if the same version of the teamwork MDAC and the administration MDAC are selected.

Upgrading the teamwork MDAC

To upgrade a teamwork MDAC, the following operations must be carried out.

1. The repository administrator selects the new teamwork MDAC. The following dialog box may appear (Figure 9).

Figure 9. The "Migration" window

If this window does not appear, MDAC selection has been carried out successfully, the new MDAC is compatible and all users can immediately upgrade to the new teamwork MDAC.

2. If this window appears, it is first advised that each repository user run a project check-in and that a repository backup be carried out. No users must be using the repository. All databases should be closed except for the repository administrator database. The repository administrator must then select the new administration MDAC. The following dialog box will then ask him to migrate the repository (Figure 10).

Figure 10. The "Migration" dialog box

3. Click on the "OK" button. The repository will then be migrated.

4. After migration, all users must update the teamwork MDAC to the new version. Failure to do this will cause the first window (Figure 9) to appear for teamwork MDACs 4.3 versions or above.

Note: Version 4.2.d or earlier of the MDAC must NEVER be used on a repository created using the 4.3 version, as no checks are carried out by the earlier teamwork MDACs.