For class interface parts, the following rules apply to
writing part information statements. These rules apply in
addition to the general rules for all part information.
- The following statements are required for a class
interface part:
- VBBeginPartInfo
- VBComposerInfo
- VBEndPartInfo
- The part beginning statement must appear first and the
part ending statement must appear last, as follows:
- VBBeginPartInfo
- ...other part information statements
- VBEndPartInfo
- The part names on the VBBeginPartInfo statement and
VBEndPartInfo statement must match. All part names must
be unique and be valid C++ class names.
- The part type on the VBComposerInfo statement must be class.
- All feature names (attributes and actions) within a class
hierarchy must be unique. If duplicate feature names
exist, the information for the derived class is used and
the information for the base class is ignored for that
specific feature.
- Attribute and action interface statements can appear more
than once for a specific part, but all other interface
statements must appear only once. Most implementation
statements can be used more than once within the part
information for a class interface part.
You can use the following part interface statements for class
interface parts:
Defining the Part
Interface Using Part Information Statements
Part Information Statements and
Files
Example Class Interface
Part Information Statements for IRange