|
Merge data from .gpn files |
  
|
|
Merge data from .gpn files |
|
As mentioned in the previous chapter, it is necessary to transfer the data from the database to a .gpn file to be able to work offline. Untis MultiUser offers a convenient tool to transfer data that has been changed offline back to the database without overwriting all the changes that were done by other users in the meantime in the database.
Caution!
Merging data from a .gpn file with a database works only if the .gpn file was exported from the MultiUser mode. If the .gpn file was not compiled this way then the menu item is inactive. You can merge only into this set of data that you have exported from. If this set of data is not existing any more the following error message appears.
A complete work cycle looks like this:
| 1. | Export the data from the database into a .gpn file. |
| 2. | Now you can work in both sets of data independently of each other. |
Caution!
You must not change the terms, otherwise the merging of the data cannot be processed. Ensure that changes of terms are done before you start the export to the .gpn file.
| 3. | When the two sets of data shall be combined, open your .gpn file and choose the menu item "Modules | MultiUser | Merge in database". |
| 4. | A dialogue appears in which you have to enter your user name and your password. If the function "Log in after completion" is activated, you will be logged in automatically after the merging in. |
| 5. | Now Untis examines every table in the database if there are changes with regard to the data in the .gpn file. For each table which includes changes (master data, lessons, holidays etc.) a dialogue appears in which you can choose whether the change shall be carried out or not. |
Let us have a look at the following example:
In the columns "in gpn" and "in DB" you can see whether this element exists in the . gpn file or in the database respectively. So the teachers Gauss, New and Arist exist in both sets of data. The user "Administrator" (see column "User") has changed Gauss and Arist in the database which is indicated by the red background. Teacher New's data has been changed only in the .gpn file that is why there is no red background.
The element Tea2 has been created only in the database whereas CC has been created only in the .gpn file (or they have been deleted in the respective other set of data). Accordingly either the box "in DB" or "in gpn" is ticked but not both of them. Choose via the column "Apply" the changes that you want to transfer to the database. After that activate the button <Merge selected elements>.
Caution!
The tick "Apply" always refers to the .gpn file. If you tick all elements then all the changes that were made in the meantime in the database will be deleted. In this case you would erase teacher Tea2 from the database.
Merely the elements that have been changed are displayed, it is not shown which kind of data has been changed (time requests, codes etc.).
Alterations in the views in Untis or cover planning are not applied.