The global fields appear to be functioning exactly as they have been designed to do. Any changes made to the value of a global field do not persist when made from a client of the hosted database. The values revert to their original values when the file is closed by the client. To make a persistent change to the value of a global field requires making that change from the context of a host session on the database. There are several ways to achieve that:
- Take the file down off the server, open it in FileMaker Pro directly. Change the values and return the file to the server.
- Use the server's admin console to run a scheduled script to modify the values.
- If hosting with FileMaker Pro, go to the host machine and modify the values.
- If using FileMaker 13, the new Perform Script On Server script step can perform a script that runs on the server and thus makes a persistent change to a global field.
Clients will not see the change made by options 2 -3 until they close and re-open the file.
See this knowledge base article: http://help.filemaker.com/app/answers/detail/a_id/3604/kw/global
Many thanks, If I 'd wrapped my head around the notion of global fields more, I 'd have gotten there, alas I remained perplexed. I ll try any of the methods. Btw, I took the db off the server today to change remote storage, and did the work there with global fields too.
I need to buy you a beer or 10 Phil, thanks again.