if i wanted to guarantee the values in a global I would explicitly set them in a script and run that script on first window open.
If you want to reply on the stickieness of a global you simply open the file with FM Pro, set the global field to whatever value you want to stick and close the file.
When you reopen it the global will show the value from right before you closed the file.
The only thing to remember is this is only true when the file is opened locally (not when hosted on FileMaker Server).
But the values change from time to time, so that woukd not work and at least from my pount of view it does not make sense.
Its database and a database should not loose values in its database otherwise it should be named datatrash?
Globals are a special type of field and knowing how they work is an essential part of the took kit for FileMaker.
They are expressed as fields in a table but do not behave like a field.
They are not trash in any sense of the word
but why does one pair behave totally different? the other work great (actually I have 10 that work and only 2 that dont work)