A couple of notes.
1 - Using a Property instead of a variable declared as public in the Process_Globals, has some advantages:
1a - in the two routines that usually make up a Property, you can obviously write code and therefore check that the value set is valid;
1b - while you cannot prevent the value of a public variable from being changed, you can do it with a Property, creating only the setting routine (setXXX but not getXXX);
2 - another important difference between a normal public routine and a Property (its "set part") is that only the first one can receive more than one parameter.
3 - I forgot the others I wanted to write, "listening" to the TV news ?