We have a global field in one of our databases that never seems to "remember" when new data is typed into it. The next time the database is opened, the field defaults to the old value. It's shared by FileMaker Server, but we used to have the same problem when it was shared by a regular version of FMPro. Any ideas? I'm about to give up and write an opening script that resets the field automatically, but that shouldn't be necessary.

What you're describing is normal behaviour for global fields in a networked solution.

See my recent post at:

Globals in Multi-user solutions

for a discussion of some options and alternatives you might want to consider.

Maybe the Global is still using a previous field option. e.g. if the Global was a text field once and it had an auto-enter it will still work if you change te type to global.

rrrichie said:...if the Global was a text field once and it had an auto-enter it will still work if you change te type to global.

Hi rrrichie,

I think you are probably thinking of validation options, not auto-entry options.

Validation settings will still work if a field is changed to global, but auto entry options have no meaning in relation to globals and are not retained. This is because auto entry options are invoked when a new record is created - but a global field does not belong to a record so there is no point at which auto entry options can be invoked.

...And validation options - whether they were in force or not, would hardly be likely to account for data dissappearing when the file is closed and re-opened, whereas the explanation I offered definitely would.