Global Field Problem

[Toddski]

I inherited support for a database and a user deleted some data that I then restored from a backup.

Well, now I have a global field that has data immediatly when I open the database. I ran a design report and that field is not set until you run the script set for exiting the database.

Why does the global field now open with a default value?

Thanks

Todd

[mr_vodka]

See if this FAQ helps.

http://faq.filemakermagazine.com/index.php/Global_fields

[Toddski]

Well it helped slightly with my understanding however this database is now hosted in a FM server so the session ends when they log off and the globals should reinitialize when they start again. For some reason the globals are not reinitializing.

[mr_vodka]

I think you may be missing the point... It will display the value of the global field at the time that it was hosted. So if you went to a backup and lets say you opened it locally. With an opening script, it could have easily set a value to that global field. Then when you go to host it, it will have its last value.

It is important when having an opening script that sets global fields, to be careful when opening it locally since it will set default values which you may not want when being hosted.

[Toddski]

Ahh light bulb!

I see exactly what you are saying. I can write a script to empty the global when the database opens. That is what is suppose to be in the global in the first place.

Thanks.