Member part does not have an attached cross section occurrence - Intergraph Smart 3D - Administration & Configuration

Intergraph Smart 3D Database Integrity Administration

Language
English
Product
Intergraph Smart 3D
Subproduct
Database Integrity
Search by Category
Administration & Configuration
Smart 3D Version
12.1 (2019)

Message

Member part does not have an attached cross section occurrence.

Severity

Crucial.

Detailed Description

Every member part must have only one related cross section occurrence that defines the projected profile for the initial solid geometry.

Possible Cause

In Version 4.0 of the software, a cross section services function was delivered that allows the ability to share the occurrence of an existing member part. This function is called PlaceCrossSectionOccurrence. By setting the third argument of this function to False, the developer can indicate that an existing cross section occurrence is to be used instead of creating a new one. The problem is that the developer cannot delete the cross section occurrence because it can (and will) delete the cross section occurrence out from under an existing member that shared the occurrence. This services function typically is used within hangers and supports, stairs, ladders, and handrail Visual Basic custom commands where the cross section was retrieved to produce a projection and then deleted.

Possible Impacts

The software cannot modify the member part that lost its cross section occurrence.

What You Should Do

There are two items to clean: (a) existing member parts (b) existing Visual Basic commands.

The steps to clean the existing member parts are:

  1. Open the model.

  2. Select the member part, and click Properties on the ribbon.

  3. Select the Cross Section tab.

  4. Choose a new cross section in the Section Name box (preferably a larger section of the same type as the original).

  5. Click Apply.

  6. Restore the section name property back to its original value by selecting it in the Section Name box.

  7. Apply the properties, and exit the dialog box.

The steps to clean the VB commands to prevent this error from occurring again are:

  1. Search all VB code for the function PlaceCrossSectionOccurrence.

  2. For all located calls, change the third argument to True.

  3. Verify that after the call to PlaceCrossSectionOccurrence, when you are done using the occurrence, you delete the occurrence from the database; otherwise, you will be leaving orphaned cross section occurrences in the database.

  4. Rebuild your VB code.