Page Comparison

...

FUNCTION xpfImportStepFile (STEPfile        : STRING; 
                            logFile         : STRING; 
                            repositoryName  : STRING;
                            modelName       : STRING; 
                            schemaName      : STRING; 
                            shortNamesFile  : STRING; 
                            options         : INTEGER
                            VAR sdaiError   : INTEGER) 
                            modelId         : GENERIC;
                

The xpfImportStepFile function imports a STEP Physical File into EDMdatabase^. Normally the imported data set will be stored in a new data model. Optionally the imported data set can be added to an existing data model.
This function returns the modelId that uniquely identifies a data model populated with contents of the imported STEP Physical File by the xpfImportStepFile operation. The constant xpxNullId will be return when no population is made by the operation.
The Express schema that defines the structure in the Data Section of the actual STEP file must exist as a dictionary model in EDMdatabase ^ before this function can be successfully executed. The name of this Express schema is found in the attribute FILE_SCHEMA.SCHEMA_IDENTIFIERS in the Header Section of the STEP file. See EXPRESS below.
The STEP Physical File format is defined in to ISO 10303-21: Clear text encoding of the exchange structures. A STEP Physical File is also referred to as a Part 21 file.
This is one of the implementation forms of ISO 10303, and can be used to exchange data between two EDMdatabases or between the EDMdatabase ^ and any application that conforms to ISO 10303-21. The STEP Physical File format is also suitable for long time archiving of data.
Options are identical to those used by edmiImportStepFile but are prefixed by XPX.
When the option KEEP_STEP_IDENTIFIERS is enabled, a STEP Identifier model is created and connected to the data model created by this operation. The purpose of this STEP Identifiers model is to hold the correspondence between the entity instance identifiers on the actual STEP file (stepID) and the related instanceID in the EDMdatabase^.
No STEP Identifiers model can be created when the XPXADD_TO_EXISTING_MODEL option is enabled.
The STEP Identifiers model will be opened for read only access when the related data model is opened, and the STEP Identifiers model will be deleted when the connecting data model is deleted. The STEP Identifiers model can also be handled as an individual model with respect to the EDMdatabase ^ operations.
A STEP Physical File can be created by the edmiWriteStepFile or xpxWriteStepFile function.
The xpfImportStepFile operation is very similar to the xpxReadStepFile operation except that arguments that is no longer valid for the read STEP file operation are omitted and some optional arguments are given a default value in the xpfImportStepFile operation.
For information on the format of the file in argument <short names file>, see Short names in the EDMsupervisor^ User Guide.
This function is equivalent to the EDMinterface^ function edmiImportStepFile.

Arguments

...

Return Value

...

Options

...

Example

...

<Missing Example>

See also