I am serving (FM Server 8 on Windows 2003 server) a database with global fields that users can change/update. The problem is that when the users quit out of their FM clients, the numbers go back to what they were before they changed them. This happens to me also (I am an administrator). If you turn off the FM Server service on the Windows 2003 server, and open the file with FM Client from the server shared folder, you can change the numbers in the global fields, and the updates stay. Anyone else run into this problem?

Hi Swillette

Welcome to the forum.

This isn't a problem but in fact the way globals are supposed to operate. In a shared environment they will always revert to the values that they last had when opened as a single user.

Phil

Edited September 27, 200619 yr by Guest

But their main advantage (as i see it) is that they are session specific, that is to say in a multi-user environment each and every user has for all effective purposes, their own global field -- i.e. if a user changes the value, it changes only for them, not for any other user and will revert when that session ends (when the file is quit.

Correct. That's their intended purpose. The global storage is basically a place to store values temporarily. With the introduction of FileMaker Pro 8 and script variables, their use as storage venues has diminished considerably, although not completely so.

Steven