Have a solution hosted on a Filemaker Server 8.

Have a table (Constants) used to hold global fields.

One record. When I open layout on hosted solution and enter data in a field all is well. When I close the solution and reopen it the new data does not save. If I open a copy of the same file as a local file and enter data and close then reopen it the new data is there.

Why?

Globals are only stored in the database when the file is opened in single user mode (non-hosted)

Some developers use this effect to store global variables or 'default values' but down side is that you have to take the system off line to modify the values.

The better approach is to use a preferences table with one record and real fields,

then transfer these values to a variables or globals on startup.

Globals are only stored in the database when the file is opened in single user mode (non-hosted)

Some developers use this effect to store global variables or 'default values' but down side is that you have to take the system off line to modify the values.

The better approach is to use a preferences table with one record and real fields,

then transfer these values to a variables or globals on startup.

Thanks for the quick response.

I would add a preferences table and in the startup script, I 1)capture that data as global variables or 2)use the preferences table to set the data in the global fields?

I prefer global variables unless some data is used for user interface like images etc. you could use global fields for them - or if you need some global key field to be used for a relationship.

here was one technique.

http://www.filemakermagazine.com/videos/using-global-graphic-variables.html