The Export Process

Exporting from the base product all items are exported using millimetres as the distance units.

All reference data, such as any pre-existing reference model from the current session are removed before exporting anything. for further information on Importing and for further information about saving the reference model, refer to Import from AVEVA Bocad Steel.

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 AVEVA Bocad Steel?

• Is there a valid Steel Standard table?

In addition, there is an specific UDA, :FABEXCLUDE, attached to certain base product elements by which you can define whether the item is to be exported or not. Setting this logical flag to true will exclude 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. This waiting time is user 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 will be asked if to carry on waiting for another time unit.

Click Yes and the interface will wait for another period of time. Click No to stop the interface where it is. Finally the system will indicate its completion, whether successful or not. This completion message should be read in conjunction with the log file, if any errors are indicated (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 will bring up a File Browser, or by clicking Save as to the suggested filename. Either way, if the file already exists, you will be asked whether to overwrite it. The log file window may then be closed by clicking Cancel.

If the Brief mode has been chosen on the Run Information window for displaying the log file, the window displaying the log file will filter out all Warning messages, leaving only the Error messages. Saving the log file, however, all messages will be retained in the file.