A global global...yeah, I've been asking for that for a while...
Rather than a related table, I will simply make a stand-alone table called "Globals". This table has only one record and it consists of non-global fields.
On startup, my opening script goes to that table (layout actually) and SetField's the globals I want to the values in that table. This lets the globals exist across user sessions...not really to exist, but to be re-set on startup.
You could have the pertinent fields of the "Global" table show up if you wanted to change them...simply open the window showing them, change them, then close the window.
I had actually had the exact same thought you did. But because I was being "lazy" I tried to move the data back and forth from the global fields I had already created to the regular fields in my global table. This process didn't work. When I actually changed all my field references in scripts to the regular fields in the global table it works fine.
Thanks for the tip!