Export Process

Exporting from the application, all items are exported using millimeters as the distance units.

All reference data, such as any pre-existing reference model, is removed before exporting anything. Details about saving the reference model are available. Refer to Import from SDNF for further information.

Prior to any Export process, all fields are checked for validity.

• Is the output file named?

• Is anything going to be exported?

• Are the mapping tables compatible with the Target Package?

• Is there a valid Steel Standard table?

In addition, there is an SDNF specific UDA, :SDNFEXCLUDE, attached to certain application elements by which you can define whether the item is to be exported or not. Setting this logical flag to true excludes the item from the Export process. Refer to UDAs for further information.

Before continuing, the Export process polls all the Configuration objects for the high water mark on Transfer and Revision numbers. It then updates the object applicable to the current MDB and user to contain the latest Transfer value.

The list of all items listed in the Export list is then stored on Header element.

After verifying that all the data is correct and valid, the external program is called. The interface waits for a certain time until the program is finished. The amount of waiting time is configurable. If there are errors raised by the external program you are notified and more detailed information is placed in the log file. If the waiting period expires without the interface detecting that the external program has completed - it may have crashed, or even not exist, you are asked if to carry on waiting for another time unit.

Click Yes and the interface waits for another period of time. Click No to stop the interface where it is. Finally the system indicates its completion, whether successful or not. The completion message should be read in conjunction with the log file, if any errors are indicated.

The message indicates a successful completion.

The error message indicates that a problem was encountered in the external program.

On completion of the external program, the status file is inspected and, if the result is favourable, you are then asked whether or not to view the log file, if that option has been selected on the Run Information window.

To inspect the log file later, save it with the File > Save as option in the File Viewer window which opens a File Browser, or click Save as to the suggested filename. Either way, if the file already exists, you are asked whether to overwrite it. The log file window may then be closed, click Cancel.

If the Brief mode has been chosen on the Run Information window for displaying the log file, the window displaying the log file filters out all warning messages, leaving only the error messages. Saving the log file, however, all messages are retained in the file.

Error and Log File Messages