|
Saving to .gpn files |
  
|
|
Saving to .gpn files |
|
Sometimes it is useful to save the data which is stored in the database in a .gpn file. E.g. the timetabler wants to work at home on the weekend where he does not have a connection to the network.
Regarding the views, the following rules apply:
| • | During the export to a .gpn file all private views of the active user as well as all public views are written to the .gpn file. |
| • | If you create new views in the .gpn file and you transfer the file back to the database then the new views will be stored as a private views. |
Caution!
The public views are internally marked as such in the .gpn file too. If you mark views as public in the database after the export to the .gpn file then you will loose the changes when you transfer the .gpn file back to the database.
Changes of the views are not considered when you merge data from a .gpn file with the database.