Global fields are session specific when running a file on FileMaker Server, where as databases run locally of the users machine the contents is stored, so if you wanted a hosted file to always hold the same value in a global you would need un-host the file and open it on a local copy of FileMaker and close it, then re-host it.
However for what you want, where you modify the contents regularly, the simplest solution to implement would be to include a Set Field script step in a start-up script that sets the global field as users go into the database. You would just need to edit this script step when the news changes. Do you have a script that runs when the database is opened?
Or create a single record table that is related to the TO of your startup page and display the field with the announcement from that table instead of the global, but if you would prefer not to have an additional table then the startup script would be the way to go.
Let me know which you would prefer and if you need me to I can walk you through it.
Thanks for the ideas. I had thought that the globals were session specific, but was not sure.
Your second idea is similar to the best I had come up with before posting. Startup page would be the single record table showing announcements. "Enter" button takes user to the main menu of the existing table.
The script step edit would possibly take longer than the layout edit I'm doing now.
I'll leave this open to ideas for a while. Thanks.
I went with the single record table method.