I am not quite sure what you are asking. Typically you select an automation server and object class in which you are interested. Whether you can instantiate an object for your selected class is determined by the programmer of the server.
For example, the only TestStand class for which you can instantiate an object is the Engine class. Other TestStand objects must obtain through methods of the Engine object and objects you obtain from the engine object. This relationship is defined by the programmer of the ActiveX server.
When you are able to instantiate an object for a particular class, you can save a reference to this object in a TestStand ActiveX variable. You can then use this reference in subsequent steps to invoke methods or properties on the same object. In t
his case you only create the object once in your first step.
If you want to create a different object for every step (make sure this is necessary since it is a lot of overhead), then you can do so. If you want all the created objects to co-exist after they are created, then you will have to assign their references to different variables. If you only want one object to exist, you can reuse the same variable to store the references. When you store a new reference in a common variable, the old reference is properly released (object terminates).
Good luck.
