|Download Help (Windows Only)|
You can use only one version of a type at a time. TestStand uses the version number of a type to determine which version of a type to use when opening a file that has a different version of the type than the version currently in memory. Typically, the version of the type with the latest version number is the version that TestStand automatically uses.
In versions of TestStand earlier than version 4.1, the propagation of unwanted type versions between files could occur when you open a sequence file with a version of a type later than the version of the type in a type palette file. The automatic type conflict resolution in TestStand updated the type palette file and every file you subsequently opened to use the later version without warning or notification.
In TestStand 4.1 or later, if the type is in a type palette file, the latest version must also be the version in the type palette file and the earlier version must exist in a file other than a type palette file for automatic type conflict resolution to occur. This behavior avoids propagation of unwanted type versions. You can modify the behavior to become more or less strict by changing the value of the Allow Automatic Type Conflict Resolution option on the File tab of the Station Options dialog box.
Use the Set Earliest TestStand Versions that can Use this Type option on the Version tab of the Type Properties dialog box to specify the earliest TestStand version that can use a type to prevent the TestStand Engine from using the type when the version of the engine is earlier than the TestStand version you specify. When you enable this option and an earlier version of the engine attempts to load the type, TestStand ignores the type and loads the file only when an earlier version of the type already exists in memory. If you do not specify the earliest TestStand version that can use a type and you set the Allow Automatic Type Conflict Resolution option on the File tab of the Station Options dialog box to Always, future versions of a type might propagate into type palette files and sequence files that run in the previous TestStand version.