Hello Aaron,
As you may have already noticed, all the steps in TestStand have properties that store specific information. For example: the module you are calling, or the ActiveX server you are calling.
When you create a step programmatically, you need to fill all of this properties in order for the sequence to work.
For activeX servers, there is a property named TS.SDATA.CALL that stores all the information regarding the server you want to call. To call servers already in memory, you need to have a ActiveX reference to this server stored in a TestStand variable (ex. a Local Variable) And set this variable to TS.SDATA.CALL.ObjectVariable. You may also change the TS.SDATA.CALL.CreateObject property to not create another instance of the server.
I
guess the easiest way of figuring out what to put in each property is to manually create a step and configure it to use your server (right click on the step and select specify module). Then you browse the tree view and check the contents of all the TS.SDATA.CALL properties.
Once you know what to put in each property. You can incorporate it in your MFC code.
Roberto Piacentini
National Instruments
Applications Engineer
www.ni.com/support