Hi Viko,
You should only have one TestStand Engine control (add the TestStand API 2.0 component group to your palette) in your VB application and it would be most convenient to place it on your Parent MDI Form (it won't be visible at run-time). With the engine control on your parent form you can access the engine's methods and properties from any code module in your application by using statements like this:
parentForm.Engine1.NewExecution clientSeqFile, MainSequence, parallelModel, False, 0 ' This will launch a new sequence execution
Also, since your parent form will always be loaded during your apps execution it would make sense to have the engine control on it so that the UIMessage Event handler will remain intact at all times.
Jason F.
Applicatio
ns Engineer
National Instruments
www.ni.com/ask