Locking a sequence file

[RayFarmer]

Hi Pat,

Thanks for the info. I wasn't sure about the Saving of the File. The resetting of the protection, well that was an act of desperation when things weren't going as planned.

I'll give Scott's link ago.

Regards

Ray Farmer

[icastillejos]

Does anybody have the patch??? it was removed from NI's FTP

Thanks,

[Patrick_P.]

Hey N,

I believe you also emailed in regarding this patch.  If you haven't emailed in or you don't receive an email with the patch in the next day or so, post here again, and I'll see what I can do.

Message Edited by Patrick P. on 05-03-2007 01:14 PM

[icastillejos]

Hi Patrick,

I got the patch from NI via email

Thanks,

[mrbean]

Is this issue now resolved in TestStand 4.0?  If not, I guess I need the patch also.

[AllenP]

This has been fixed in TestStand 4.0.

Allen P.
NI

[mrbean]

We have a situation where, during several test steps (of type multinumeric), instead of embedding the upper and lower limits of a step in the SequenceFile itself, we read these from a configuration file (we make use of LabVIEW's Configuration Property Editor).  Anyway, in those cases, our VIs write back to TestStand to set the upper/lower limits (using the Sequence Context) so that TestStand can (at the end of the step) make the determination if the test passed/failed. However, if a sequence file is locked, will it allow you to write to it (temporarily, during the test).  If it does, then at the end, will it prompt the user if they want to save the file?

[RayFarmer]

Hi,

Locking the sequencefile doesn't stop you from modifying the runtime values. If it did, that would mean steps like the PropertyLoader wouldn't work.

Because you haven't changed the Count value, which signals that the sequence file has changed, you will not be prompted to save the file.

Regards

Ray Farmer

[mrbean]

Are you referring to PropertyObjectFile.IncChangeCount ?

[RayFarmer]

Hi,

Yeah that would be one, you would use that one if you were working on the PropertyObjectFile. I think there is a similar one SequenceFile.IncChangeCount.

Regards

Ray Farmer