Type Mismatch, Bypass Message?

[Mikef]

We have a very large number of test sequences written (~600) that all use the existing TypePallets.

Anytime there is a change (between any of the 5 or so workstations) we get the "Type Mismatch" message and are required to select to either use the existing types or use the loaded types.

Another problem is, that we use a large number of FileGlobals that contain parameter names and enumerations.  When there are changes to our system and we would like update the FileGlobals to include the new parameters.  Additionally, I want to be able to modify some of the steptypes (step colors, add new, etc.)

I'm trying to figure out a way to get all of our TestStand Sequence files checked out of SourceSafe, Opened, Updated, Saved and checked back into SourceSafe.

     Problem is, when you open each file, there is the "Type Mismatch" popup that requires a user to click.

Is there a way to automatically select the "Use Currently Loaded Type" so that we can automate opening each file, Updating, Save and close them?

   I've found that there is a limit of somewhere around a hundred files that can be opened at any one time (to update manually), before TestStand crashes.  (and it takes a LONG time to open them!)

Mike

[Manooch_H]

Hi Mike,

You can use the TestStand Type Differ to merge all of your Sequence Files with the Sequence File or type file that contains the types you wish to be using. The TestStand Type Differ is part of the NI TestStand Toolkit for Large Application Development located on ni.com/labs.

The Type Differ can be used to convert all of the types in the files that you choose to match the types in the particular file you specify. I encourage you to look into the TestStand Type Differ while investigating methods to achieve your above mentioned goals.

Hope this helps!