having an "execution global"

[ebalci]

FileGlobals are fine but -as I read from a previous post- after each execution that changes them, the file itself is modified, which is not very desirable for me.

So there is a run-time copy and a static copy. Run-time copy is generated from the static copy at the beginning of an execution, and at the end, the (probably modifed) run-time values are written back to the static copy, which resides on the hard drive. Therefore file is overwritten and its date and time properties (in Windows) are modified.

Can't we still have some variables that :

• are initialized to the values assigned in the editor at the beginning of an execution,
• are available throughout the execution,
• are simply discarded at the end of the execution (after the report is generated for example), and
• are not carried to the next execution (cleans its own mess)

Actually, the only thing we need to do to have a clean start is to initialize them at the beginning and that is not much of a big problem, I can live with that.
But my major concern is the file being modified.

[RayFarmer]

Hi,

[So there is a run-time copy and a static copy. Run-time copy is generated from the static copy at the beginning of an execution, and at the end, the (probably modifed) run-time values are written back to the static copy, which resides on the hard drive. Therefore file is overwritten and its date and time properties (in Windows) are modified.]

There is a static copy and a Run-time copy. Correct so far. Under normal operation the runtime copy does not over write the static copy and therefore when the execution ends, the runtime copy is finished with. The static copy remains untouched.

What you may have been reading in other posts, is where others actually want to change the static copy. This you have to do by modifying the DefaultFileGlobals ( not the exact wording of this property) under program control, which you will not be doing.

I hope this helps

Regards

Ray Farmer

[AllenP]

This is incorrect.  A file global is only written back to the edit time copy if you have either set the file global's flags to be "Shared".  No file is modified.

It sounds like FileGlobals do exactly what you want without any modifications.

Allen P.
NI

[James_Grey]

>> "This is incorrect.  A file global is only written back to the edit time copy if you have either set the file global's flags to be "Shared".  No file is modified."

The SequenceFile Properties>>All Executions Share the Same File Globals setting does not affect the edit time copy.

Set this option to specify that all executions share the same runtime copy of the file globals in that file. Otherwise, each execution get it own private runtime copy of the fileglobals for that file.  This option is a convenient way to share information between cooperating executions. The default is to NOT share.

[ebalci]

Gentlemen,

Thank you for the replies. I was very close to my -almost- first disappoinment with NI software.

I feel really relieved now..