Application Export Window
You can set in the dialog for application export:
1) Which part of the application to export:
-
Complete application - all application components are exported with the exception of those that are excluded from export at the Properties tab in the Output window;
-
Object changed since: - exported are only objects that were modified or created after the specified date (including this date), with the exception of those that are excluded from export at the Properties tab in the Output window.
2) Export specification:
-
Include table data - if this box is selected, relevant data in the internal format will be also exported together with table definition. This is not true for tables where data export is explicitly prohibited.
-
Include privileges of roles - if this box is selected, privileges to objects and data assigned to application roles are exported together with application. Even in the case when table data are not exported (the previous switch), privileges to these data will be exported.
-
Include privileges of users and groups - if this box is selected, privileges to objects and data assigned to users and groups are exported together with the application; however, users and groups are not exported (they are not a component part of given application!).
-
Encrypt - export of objects that were marked on the Properties tab in the Output window (the Protected object box), will be executed in unreadable format. They will be also stored in this format at the server after the next application import, i.e. their definitions will be readable solely for this application. This export alternative serves for security of developerīs work against the other users. This option must be also used when exporting an application that was encrypted earlier. Details - see Locked application.
After selection of the export alternative, you must specify the path for the definition file of the exported application (APL file).
The application components are exported to the same directory, where the application definition file will be created. Each component will be in a separate file. File names consist of object names without diacritical marks (details see in APL file description). If data from tables are also exported, their export is done in the internal 602SQL format. If a file with identical name already exists in the same directory, you will get a warning.
