Hi Drew,
I think Dennis might have come at this from the wrong angle.
Have a look at the example that ships with TestStand under
\Examples\SequenceBuilderTool\LabVIEWThis might give some clues, but I'd suggest posting this question over to the TestStand discussion Forum as suggested by Dennis.
There'll be a few more people there who can help a bit more in-depth
My personal suggestion is to create a custom step type that calls the .vi's and then you can create the steps in a new sequence file using your tool easily. This could be cumbersome for you if you already have a lot of steps setup.
Better then to create a resource to get the steps out of to clone them by creating a sequence file which is full of your steps. When you have a handl
e to a cloned step, you can change properties about it in memory, before putting it into the sequence (i.e. change it's name and stuff)
Otherwise you need to get the type and create a new step of this type.
If all you're stugling with is the module to call, then for the step you have a handle to, change the
you can either change the "Step.TS.SData.ViPath" as a string (TestStand set property value String with a reference to the sequence_context) or if you wanted to bring up the specify module dialog, if you have a handle to the step itself, call the method SpecifyModule.
Hope that helps
Sacha.
// it takes almost no time to rate an answer