Global fields seems to be related to the client using them and adding to the field stays as long as the file is open. On reopen they are reset to blank.

I have some global fields that I wish all users to see/edit the same all the time.

The only way I have been able to partly get around this is to set them on the host file first.

Now that I am trailing the server version this is not possible as the host isnt accessed directly. Is this a limitation of globals or is there some other way? Thanks

Edited March 6, 200817 yr by Guest

Common practice is to create a one-record table to store your "startup" values. On startup, run a script to load them into the globals.

I have some global fields that I wish all users to see/edit the same all the time.

If this is the case and you want your users to see the live changes immediately, then globals are not the way to go in the current scenario.

However, if you are okay with your users seeing the new values on startup, then you can use a preferences table and set the globals as Tom has said.

Seems like the separate table for those items is the way to go

the global preferences table discussion is here: http://fmforums.com/forum/showtopic.php?tid/172700/post/188596/#188596