Locking a sequence file

[Troy12]

Hi,

Is it possible to lock TestStand sequence files so that it's not editable or viewable?  I am using TestStand 3.5 and before distributing I wanted to lock the sequences.

Any comments/suggestions are appreciated. Thank you.

[Norbert_B]

Troy,

with TS 3.5 you have the possibility to protect your sequencefiles.
Just open your sequence with the sequence editor and select Edit >> Sequence File Properties. Change to the Advanced-tab and select the type of protection you'd like in the "password protection"-area.

hope this helps,
Norbert B.

[Troy12]

Thanks!

If I set the sequence to 'not viewable' and lock it, is there any way at all to view or edit the sequence without the password.

Your response is appreciated.

[RayFarmer]

Hi,

Doesn't look like it, not even if you open it up in a text editor.

The only other way is maybe from the report thats generated.

Regards

Ray Farmer

[Troy12]

Thanks.

I have over 100 sequence files to be locked.  Is it possible to lock all sequence files together (like mass compile)?

[RayFarmer]

Hi,

I was going to say, "write a sequence file to lock all your seuqnce files"

But having played with the API's (TS3.5), I find it doesn't appear to be that straight forward.

If I start with a file that is unlocked. I can lock the sequence file but I cannot save the file.

If I start with a file that is already locked, I cannot appear to unlock it even when I am using the same password.

Anyway I have attached my example.

password is set to abc

the sequence file name is Sequence File2.seq which is placed in the location of the example sequence file attached.

See if anyone can spot the problem.

Regards

Ray Farmer

[Troy12]

Thanks for your time, Ray.  I will check it out.

NI Application engineers may have some answer.

[Scott_Richardson]

Troy -
Unfortunately there is a bug in the PropertyObjectFile.Lock and Unlock API methods that we found that prevents you from using the same password between the API and the Sequence File Properties dialog box. The bug is in the engine so you must patch TestStand 3.5. I have placed a temporary file at ftp://ftp.ni.com/outgoing/TestStand 3.5 40HFFL00.zip that you can download. The readme in the file has instructions on how to manually apply the patch.

[Patrick_P.]

Hey all,

I wanted to clarify a few points about the example as well.  You do not have to save the sequencefile if you are calling the lock or unlock method.  These methods both modify the sequencefile itself on disk.  Also with the unlock method, it is not necessary to reset the protection property.  Once the file is unlocked you are good to go.  Thanks for posting the example Ray, and I like the new personal icon 🙂  Hope this helps to clear things up a little!

[James_Grey]

I would not be surprised if a future version of TestStand includes a feature that can lock or unlock all your files at once.

...of course, officially speaking, I'm only making statements about what might or might not surprise me.