Hi,

I have used some global fields in a database that is shared by FMSERVER.
When changing one of these global fields I find it always returns to its
initial value next time I open the database.

Anyone know a solution to this problem?

Thanks,

-- 
Bas Holleman
Utrecht

In article <BD65D24D.799C%B.Holleman@fi.uu.nl>, Bas Holleman
<B.Holleman@fi.uu.nl> wrote:

> Hi,
> 
> I have used some global fields in a database that is shared by FMSERVER.
> When changing one of these global fields I find it always returns to its
> initial value next time I open the database.
> 
> Anyone know a solution to this problem?
> 
> Thanks,

In FileMaker Pro Global fields are not really "global" - they're
"global" to the records in the file, but are really only "local" to
each computer opening the file. In a situation where only one computer
is opening the file at a time it doesn't make any difference.

BUT, in a network / server environment the content of Global fields are
only saved by the Host computer, any changes by the computers
connecting to the host are lost when they quit. In the case of
FileMaker Server, it's Server that is the host so only it's values are
saved.

For Global fields that need to be pre-set you can enter the data in a
normal copy of FileMaker before moving the files into FileMaker Server.

For "global" values that need to dynamically change you'll have to
create a related file called 'Globals' (for example) which uses NORMAL
fields to store your "global" data values. That way all computers using
the database can save values. Depending on how you need the system to
work the 'Globals' file may only need one record accessed by all the
comuters or it may need to create a new record for each individual
computer using the database to have it's own saved "global" values.







Helpful Harry                   
Hopefully helping harassed humans happily handle handiwork hardships  ;o)

Or you can use a script that runs when the file opens to set your global
values, if you want to have easier access than having to go back to the
original file .

"Helpful Harry" <helpful_harry@nom.de.plume.com> wrote in message
news:090920042207112736%helpful_harry@nom.de.plume.com...
> In article <BD65D24D.799C%B.Holleman@fi.uu.nl>, Bas Holleman
> <B.Holleman@fi.uu.nl> wrote:
>
> > Hi,
> >
> > I have used some global fields in a database that is shared by FMSERVER.
> > When changing one of these global fields I find it always returns to its
> > initial value next time I open the database.
> >
> > Anyone know a solution to this problem?
> >
> > Thanks,
>
> In FileMaker Pro Global fields are not really "global" - they're
> "global" to the records in the file, but are really only "local" to
> each computer opening the file. In a situation where only one computer
> is opening the file at a time it doesn't make any difference.
>
> BUT, in a network / server environment the content of Global fields are
> only saved by the Host computer, any changes by the computers
> connecting to the host are lost when they quit. In the case of
> FileMaker Server, it's Server that is the host so only it's values are
> saved.
>
> For Global fields that need to be pre-set you can enter the data in a
> normal copy of FileMaker before moving the files into FileMaker Server.
>
> For "global" values that need to dynamically change you'll have to
> create a related file called 'Globals' (for example) which uses NORMAL
> fields to store your "global" data values. That way all computers using
> the database can save values. Depending on how you need the system to
> work the 'Globals' file may only need one record accessed by all the
> comuters or it may need to create a new record for each individual
> computer using the database to have it's own saved "global" values.
>
>
>
>
>
>
>
> Helpful Harry
> Hopefully helping harassed humans happily handle handiwork hardships  ;o)