Hey all-
Although I fear I already know the answer, here goes: Is it possible
to change globals on the fly in a multi-user deployment, without
logging everyone out, logging in as single user, and changing the
global in question?
Thanks,
Nate
FMP Adv 8.5 Windows

"NScheffey" <NScheffey@gmail.com> schreef in bericht 
news:1176218062.254165.50700@n76g2000hsh.googlegroups.com...
> Hey all-
> Although I fear I already know the answer, here goes: Is it possible
> to change globals on the fly in a multi-user deployment, without
> logging everyone out, logging in as single user, and changing the
> global in question?
> Thanks,
> Nate
> FMP Adv 8.5 Windows
>

I'm not quite sure but perhaps variables might be the way to go.

Keep well, Ursus 

On Apr 10, 11:14 am, "NScheffey" <NSchef...@gmail.com> wrote:
> Hey all-
> Although I fear I already know the answer, here goes: Is it possible
> to change globals on the fly in a multi-user deployment, without
> logging everyone out, logging in as single user, and changing the
> global in question?
> Thanks,
> Nate
> FMP Adv 8.5 Windows

Thank much Ursus for the input
Well, one of the globals I'm talking about is a container field for
the graphic interface of the solution, so a variable wouldn't work
there. The other is the company's street address, which doesn't change
very often, but they just asked me to put their PO Box in, and so now
I'm debating wether globabls were even the best way to handle this
from the beginning.
So at this point I'm thinking: global container fields for graphics =
good, but will need to log everyone out to change (not horrible),
global variables for company address set by a script? Or maybe one
record of non-global company information?
Thanks,
Nate

"NScheffey" <NScheffey@gmail.com> wrote in message 
news:1176219947.865568.117680@w1g2000hsg.googlegroups.com...
> On Apr 10, 11:14 am, "NScheffey" <NSchef...@gmail.com> wrote:
>> Hey all-
>> Although I fear I already know the answer, here goes: Is it possible
>> to change globals on the fly in a multi-user deployment, without
>> logging everyone out, logging in as single user, and changing the
>> global in question?
>> Thanks,
>> Nate
>> FMP Adv 8.5 Windows
>
> Thank much Ursus for the input
> Well, one of the globals I'm talking about is a container field for
> the graphic interface of the solution, so a variable wouldn't work
> there. The other is the company's street address, which doesn't change
> very often, but they just asked me to put their PO Box in, and so now
> I'm debating wether globabls were even the best way to handle this
> from the beginning.
> So at this point I'm thinking: global container fields for graphics =
> good, but will need to log everyone out to change (not horrible),
> global variables for company address set by a script? Or maybe one
> record of non-global company information?
> Thanks,
> Nate
>


For globals like the address, I use an opening script to set all these sorts 
of things. then I don't have  to go through all that closing down and 
opening single user.

In article <1176218062.254165.50700@n76g2000hsh.googlegroups.com>,
"NScheffey" <NScheffey@gmail.com> wrote:

> Hey all-
> Although I fear I already know the answer, here goes: Is it possible
> to change globals on the fly in a multi-user deployment, without
> logging everyone out, logging in as single user, and changing the
> global in question?
> Thanks,
> Nate
> FMP Adv 8.5 Windows

The usual solution for chageable "Global" fields in a multi-user
environment is to instead use a separate Table with one normal record
that has the appropriate NORMAL fields pretending to be global fields.
These of course can be accessed via a Relationship.


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

"NScheffey" <NScheffey@gmail.com> schreef in bericht 
news:1176219947.865568.117680@w1g2000hsg.googlegroups.com...
> On Apr 10, 11:14 am, "NScheffey" <NSchef...@gmail.com> wrote:
>> Hey all-
>> Although I fear I already know the answer, here goes: Is it possible
>> to change globals on the fly in a multi-user deployment, without
>> logging everyone out, logging in as single user, and changing the
>> global in question?
>> Thanks,
>> Nate
>> FMP Adv 8.5 Windows
>
> Thank much Ursus for the input
> Well, one of the globals I'm talking about is a container field for
> the graphic interface of the solution, so a variable wouldn't work
> there. The other is the company's street address, which doesn't change
> very often, but they just asked me to put their PO Box in, and so now
> I'm debating wether globabls were even the best way to handle this
> from the beginning.
> So at this point I'm thinking: global container fields for graphics =
> good, but will need to log everyone out to change (not horrible),
> global variables for company address set by a script? Or maybe one
> record of non-global company information?
> Thanks,
> Nate
>

Exept the separate table, you could also use the variables storing a 
reference to your GUI graphics. The graphics self would reside in a folder.

Keep well, Ursus 

You can also use your open script to set new define value for your Global 
field, so any one who will open the solution will have the new value set 
every time.

JF Fortier



"Helpful Harry" <helpful_harry@nom.de.plume.com> a �crit dans le message de 
news: 110420070849158148%helpful_harry@nom.de.plume.com...
> In article <1176218062.254165.50700@n76g2000hsh.googlegroups.com>,
> "NScheffey" <NScheffey@gmail.com> wrote:
>
>> Hey all-
>> Although I fear I already know the answer, here goes: Is it possible
>> to change globals on the fly in a multi-user deployment, without
>> logging everyone out, logging in as single user, and changing the
>> global in question?
>> Thanks,
>> Nate
>> FMP Adv 8.5 Windows
>
> The usual solution for chageable "Global" fields in a multi-user
> environment is to instead use a separate Table with one normal record
> that has the appropriate NORMAL fields pretending to be global fields.
> These of course can be accessed via a Relationship.
>
>
> Helpful Harry
> Hopefully helping harassed humans happily handle handiwork hardships  ;o) 

In article <4BfTh.55270$MD2.314702@wagner.videotron.net>, "JF"
<bizouman_takethisout@hotmail.com> wrote:

> "Helpful Harry" <helpful_harry@nom.de.plume.com> a �crit dans le message de 
> news: 110420070849158148%helpful_harry@nom.de.plume.com...
> > In article <1176218062.254165.50700@n76g2000hsh.googlegroups.com>,
> > "NScheffey" <NScheffey@gmail.com> wrote:
> >
> >> Hey all-
> >> Although I fear I already know the answer, here goes: Is it possible
> >> to change globals on the fly in a multi-user deployment, without
> >> logging everyone out, logging in as single user, and changing the
> >> global in question?
> >> Thanks,
> >> Nate
> >> FMP Adv 8.5 Windows
> >
> > The usual solution for chageable "Global" fields in a multi-user
> > environment is to instead use a separate Table with one normal record
> > that has the appropriate NORMAL fields pretending to be global fields.
> > These of course can be accessed via a Relationship.
> 
> You can also use your open script to set new define value for your Global 
> field, so any one who will open the solution will have the new value set 
> every time.

Using a separate table with real records will mean they don't have to
re-open the database. Simply refreshing the screen (eg. change layouts,
re-enter Browse Mode) should pull in the new values.

Of course, the down-sides are that:

    - the values are ALWAYS pulled from the server and not
      stored locally (as "Global" field values are), which
      for graphical elements on a slow computer / network
      can be annoying.

    - Find mode will be a pain. It would probably be best
      to create your own fake Find function using Global
      fields rather users using the true FileMaker Find mode.


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