Global value retention with multiple users
I have been developing single-user FileMaker solutions for a while but I am now looking to employ one particular solution as a multi-user database. My question relates to the use of global fields. I have some scripts that add data to a global field and then use that data later in the script. I am concerned that if one user activates the script, another user could also activate the same script from another record and modify the global field for the original user, with disastrous consequences.
Is there a ‘best practice’ approach to solving this problem? I assume that the use of variables would be one solution but I would welcome advice from the more experienced developers about how to ensure the database is robust in a multi-user environment.