Functional global variable shared between two exe files?

[Ola_A]

I have a very nice (?) functional global variable or procedure, that logs event text. At init I set it up with a path to a log file and a reference to a table where the text should be written.

Everywere in in the code where I need to log something I just put in the vi, with some descriptive text, and I get it logged. Works also in sub vi's etc. since all path + table ref is kept inside the function.

But a few times I have seen that two exe files with this vi seems to use the same copy of the functional global, so if I setup Path="A" in exe file A, also exe file B has path="A".

Can someone describe how this works? I am just seeing ghosts?

Ola

[Ben]

Please share some code to go with your question.

The only way that I can imagine what you described is that you are either calling the AE via VI server or are not using actual exe's but running two top level VIs in the same context.

Ben

[JÞB]

You are not seeing ghosts.  But, you do have something wrong in there if the two application data spaces are sharing a resource.  We call those types of undesired side effects "Bugs" (Its considered poor practice to write them but, sometimes it happens to even the best of us)

So lest answer the question bluntly.  No, you do not have a very nice FGV- it has a bug in it or in how it is being used.