Data can be imported into or exported from any database within your XPAC project. To import data into or export data from a database you must first go to that database. Data cannot be imported or exported from any of the scheduling screens.
| • | To import data, select File from the application menu, Import from the drop-down menu and then select Data. |
| • | To export data, select File from the application menu, Export from the drop-down menu and then select Data. |
Some points to note about importing and exporting data are:
| • | Data can only be imported into lowest level records. |
| • | Record identifiers are needed for each level of the database when importing data. |
| • | Data can be imported into any data field. |
| • | Data can be exported from any data field. |
Data is imported into and exported from XPAC databases using text files, which many other software systems can generate and read. The data import and export facilities can also be used to transfer database data from one XPAC project to another.
Some examples of data import and export are listed below.
| • | Import of geological reserves generated by a geological modelling system; |
| • | Import of geological reserves stored in a spreadsheet; |
| • | Import of equipment productivity data stored in a spreadsheet; |
| • | Import of database data from another XPAC database; |
| • | Export of database data for transfer to another XPAC database; or |
| • | Import of equipment delay times into the calendar. |
Data files
The data in the text file must be in a regular pattern for XPAC to be able to read it, however there is much flexibility in the data patterns that are acceptable. Any pattern of data that can be imported can also be exported. In general, the data should be either:
| • | Delimited - each item of data is separated from the next by a specified character; or |
| • | Fixed Width - each item of data is located within specific columns. |
The data in the text file must also include unique identifiers for the database record, used for controlling where the record is located in the database.
