ExposeToVBA or (GroupExposeToVBA)

Determines whether or not the object is exposed to VBA. Use this property improve the performance of loading, editing, and saving displays containing large numbers of objects. The more objects that are exposed as VBA controls, the longer it takes to load a display.
The default setting for this property for all new objects that are added to a display, is Not Exposed. This property is set in the Property Panel in the Graphics editor. Right-clicking on the object in the Graphics editor and selecting VBA Code will change this property value to VBA Control if the object exposes events, or Type Info Extension, if the object does not expose events. The possible settings for the property are :
  • Not Exposed
     - the object does not show up as a property of the Display object (ThisDisplay class). It also does not it appear in the object combo box of the code window. However, you can still access the object using the FactoryTalk View Display Client object model. Leave an object set to this value if you do not need to access the object in the code window using Intellisense or if you do not plan to write VBA code for it.
  • Type Info Extension
     - the object is exposed as a property of the Display object in the VBA code window but object events are not exposed. Use this setting if you do not need to write event handlers for an object.
  • VBA Control
     - the object is exposed as a VBA control, it appears as a property on the Display in the VBA code window, and you can write event handlers for the object.
    TIP:
    If you have a display with 1200 VBA objects, when you try to create another VBA object by selecting the object and in its property panel, setting the ExposeToVBA property to VBA Control, no error message regarding limits will be raised, but you will not be able to set the object to a VBA control.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal