Export & import |
A data export function is available in various Global 3000 modules to enable you to transfer data simply from Global to other systems, such as standard spreadsheet and word processing packages. An equivalent data import function is also available in the EDI module. It is planned that these functions will be extended to other Global 3000 modules. |
Scenarios |
The export and import processes are controlled by 'scenarios'. You can define these yourself and they determine: § The 'style' or format of the exported data. You can select a standard style or set up new styles using your own delimiters, escape sequences, and headings. Standard styles include both comma and tab separated variable formats with optional quotes and headings. |
|
§ The 'contents' of the exported or imported data. You can select Global data items for inclusion from those available in the data stream at the point where the data is exported or imported. You can define the sequence and format of the data items, and can optionally include constants. |
|
§ The 'data folder' and 'data path'. For exports, these control the destination of the data in the host system. For imports, these provide the path of the file to be imported. |
|
§ The 'program folder' and 'program path'. These can optionally provide export programs with details of a program to kick off in the host system on successful completion of the export. This provides a seamless link between Global and other applications; for example, when exporting data to a spreadsheet, the export program can automatically invoke the spreadsheet, so that it automatically loads the exported file and runs a macro on it. |
|
§ The name of the file which is to be imported or exported. |
|
§ Parameters to pass to the host system if a program is to be invoked; for example these can be used to specify the name of the exported file to be loaded into a spreadsheet, and a macro to be run on it. |
|
§ The 'template folder' and 'template path'. These can optionally specify a template to be passed to the program you invoke in the host system during exports. We provide a number of sample templates for Microsoft Word 97; for example to automatically insert exported statement details into a standard form in Microsoft Word. |
Note |
The option to invoke a program in the host system is only available when running Global under the Global Windows Workstation option or on a Unix platform. |
|
Standard styles and contents lists, and sample scenarios, and program, data, and template folders and paths, are provided in the standard Global 3000 Sample Data. For information about how to copy them to your live data see the Installation and Setup manual. |
|
For information about installing the sample templates, see the Installation and Setup manual. |
Scenario Maintenance |
Scenario Maintenance enables you to: § Tailor the standard styles and contents list for your particular needs. § Set up your own customised styles and contents lists. |
|
§ Set up and tailor data folders and paths. |
|
§ Set up and tailor program folders and paths. |
|
§ Set up and tailor template folders and paths. |
|
§ Set up and tailor scenarios. |
|
Each scenario specifies the style, contents list, data folder and path and file name the program is to use when exporting or importing data via the scenario. |
|
For exports, the scenario can also specify a program to be invoked in the host system on successful completion of the export, and optionally parameters and template details to pass to it. |
|
When you set up a scenario, you can choose the style to be used from a list of styles which have been defined. In the same way you can choose the contents list, data, program and template folders from lists of defined entries. So if you are not using the standard styles and contents lists, you need to define your own customised ones before you set up scenarios. The Scenario Maintenance Menu provides you with options to define each of these items. |
Further information |
§ Contents lists, see Maintain Contents. |
|
|
|
|
|
|
|