I think you are misusing globals here...
One alternative is to write a value to a one-record table and the other client should check there for the latest value whenever it needs.
Wim Hi, thanks for your response.
Indeed that's what I try to avoid (check in a related table)
I have multiple string with access (ex: wriwrrw) ,... and try to load a local variable, and avoid constant consults to a table.
pd: sorry my english
Why would you try to avoid checking a table? It does not have to be related, you can use an ExecuteSQL() call to the "settings" table, which is going to be blazingly fast since it will contain only one record, and it is context-free. That table requires no relationships to anything else.
I understand, I will apply your idea.
I tried was to avoid queries, if I have 10 users they will be made queries (consistently). My intention was to avoid those consultations (via value in local variable) but I think it makes sense what you mention, there are queries that are not so harmful.