Each MTS component can contain one or more classes which, in MTS terms, are referred to as MTS Objects. Visual Basic 6.0 provides a new property called MTSTransactionMode that can be used to set the transactional attribute for each class within the component. This property maps directly to the transaction attributes in MTS. For example, VB property value of 0-NotAnMTSObject means that this object is not MTS compatible. This property automatically sets the transaction attribute for the object when the component is added to MTS.
This property can be set to different values for different classes within the component depending on the requirements. Example of such a requirement can be if base class requires transactions while additional classes might only use transactions in certain cases.