Why does TS ask to save 'NI_Database_Types.ini' every time I quite TS?

[AllenP]

3.1.0.100 is the default version for 3.5 (and 3.1).  We have stopped incrimenting this type to allow users to modify it and keep their changes when upgrading TestStand.  Unfortunately, there is a bug that makes certain situations occur that will make TestStand think it needs to save a file, when it does not.

If you have not intentionally modified this type, you can revert it to 3.1.0.100, and save the affected files (this should modify your process model and several type palette files).  This will solve the problem.

If you have intentionally modified CommonResults, you can follow the additional steps provided in the linked post.

Allen P.

NI

[checkers18]

You said

"If you have not intentionally modified this type, you can revert it to 3.1.0.100, and save the affected files (this should modify your process model and several type palette files).  This will solve the problem."

As soon as I read in my sequence files form version 3.1, it changes the TestStand data types and leaves the loaded sequences untouched.

How do I force TestStand to update the data types in the loaded sequence files with the TestStand data types?

[AllenP]

TestStand can only load one version of a Type into memory at any time.  If a type is already loaded, and a newer version is opened, it will replace the old version with the new version.

It sounds like you have the following situation-

Your type palettes are set in the correct version (3.1.0.100).  You load an old sequence file that somehow got a newer version of CommonResults (3.1.0.9097).  This will modify all documents that use CommonResults (which is pretty much every Type Palette File, your process models, and any non-empty sequence file) that are open.

There are two solutions.  One is to open all files with the modified type into TestStand, and change the type (you only need to do this one time, once everything is open).  Save all of the files that are modified by this change.  In the event that you did not catch every file that has the newer type, you will get a prompt to save modified files (which will include all of the type palettes).  In this case, DO NOT save the type palette files.  Check to see if the version has been incrimented, revert it, and save the files that introduced the problem.

Another solution is to not worry about the modification, but use the workaround for the bug that prompts you to save, even if no change has been made.  You can do this by creating a new type palette file, and ONLY including CommonResult in it.  Make sure it is at the top of the load list.  The linked post provides more details how to do this.

Hope this helps!

Allen P.

NI

[checkers18]

Ok, That fixed it.

I don't know how the type was changed in the first place. I did not intentionally change it, and if I did, I would not have come up with a verion like 3.1.0.9097.

Anyway, that annoying message is gone and I know how to deal with it if it ever returns.

I also found an option to 'propmt me' if the types are changes so that I can choose which one to keep. I found it when I was viewing CommonResults Properties. There are several tabs, one of them is 'Version' In there I can set the choice to 'Always prompt the user to resolve this conflict' instead of 'Use the definition that has the highest version number ...'.

Is there some whay to set this as the default for ALL sequences?

[DWeiland]

Hi checkers,

You can set those preferences within TestStand by going to Configure >> Station Options >> Preferences. There  you'll find options for Auto Increment Sequence File Versions and Before Saving Modified Types.

Hope this helps checkers, have a good one.