Global values not updated/saved when database run via Server?
"When a database is run from Filemaker server, the global values are not updated on the server but are only held locally; therefore when the client disconnects, any changes are lost and any changes by one user are not seen or used by others" (from "the missing manual").
It goes on to suggest scripting the values so that they are updated each time the database is run - but as far as I can see, that means hard-coding them which would also mean a user couldn't change them.
The app I'm building uses a whole series of global values as basic settings which are then used to govern the way the app works, but these values need to be setup by the user - one example would be the rate of VAT. If I use a "normal" storage table, there has to be some risk that somehow more than one record would be created which must surely be undesireable?
Am I missing something here, or is there a simple solution to storing such a set of system settings?