Mark,
I am guessing that either you, or someone from whom you have received at least one sequence file, is using TestStand 2.0.1. However, you are probably using TestStand 2.0. Correct me if I am wrong.
If this is the case, then I believe that you are incountering a type conflict between your type palettes, your front-end callback sequence file and/or your process model. One of these files has a 2.0.1 type in it that is resulting in a type conflict.
The attached program is designed to revert your type palettes and any sequence files you select, back to using TS 2.0 types. Running this application on your files should in no way alter their functionality. After using this application, you should not have a problem launching your sequence editor.
T
he cause of this problem is explained in the following scenario. At some point a TS 2.0 user opened a TS 2.0.1 file. He was queried as to whether he really wanted to open it, and chose to do so. Upon opening certain types within his installation were automatically updated to the latest version. Specifically, Common Results and the hidden standard data type, TEInf, were updated. Since all step types use TEInf (it contains properties to store all of the step settings), all step types were marked as being changed. He then save the file as a TS 2.0 file and distributed to another TS 2.0 user. The other user then tried to open this file and received type conflicts for all step types and TEInf.
Consideration is being made as how to address this scenario. The current remedy is to revert all TS types to 2.0 types.
If this does turn out to be your problem, let me know if you have any feedback about the application, and any differences in your scenario.
Note: This application re
quires the CVI 5.5 run-time engine, which is installed on your system by TestStand. If you are running it on a system that does not have TestStand, you may have to install the CVI run-time engine.
