Hi,

I am really puzzle with the following.
I have more than 10 FM files inter-connected. I have 4 clients and all
are FM v10. The files contain many container fields as global to
introduce icons or logos. The containing of these container fields
appear as soon as a formula is true (standard procedure). Until here
everything was perfect. The global data (icons or logos) remained in
the container field (global) after closing the different clients. No
problem until I introduce an important variable, I bought a Filemaker
Server 10 and after that, everything worked smooth except that the
containing of the container fields (global) that (IMPORTANT) were
created when the server was working are not retained after closing any
client, why????

Somebody knows why the containing of a container field is removed as
soon as the client is close and open again and this happens ONLY when
the files are been served through a FM server v10? And something even
weirder is that the same kind of container fields (global) that were
created BEFORE I started to work with the server are working perfectly
and the containing are retained correctly after closing the clients.
So, the problem is just in those NEW containing fields that was
created working in the same clients that before but through the
server.

Thanks,
Jokin

Hi,
I think, from what I understand, that you are misusing the 'global' concept
: in fact 'globals' are 'local' ie personal to each workstation or user.
Then, it is normal that their content 'disappear'. I guess one solution is
to create a new file (or table) with only one record : therefore each field
of that file-table becomes available to any one anytime ie acts as a 'shared
global'. As you have many clients using the same base, I figure you want
each of them to feel as being alone : the answer then is to create the
appropriate set of scripts, fields, layouts and possibly passwords, which
will make every client to have access only to his own data.
HTH.
Remi-Noel


"Jokin" <joaquin.castilla (AT) gmail (DOT) com> a écrit dans le message de
news:53b68ba2-dd7a-40b7-8947-08ad3cf467e5 (AT) m11g2000yqf (DOT) googlegroups.com...

Thanks Remi-Noel,

I like your idea but what about to introduce the icon or logo in each
of the client? Why this is not working either? In fact, another option
would be to take out the file from the server, load the icon or logo
in the container field and put it back under the server, right?

Thanks,
Jokin

On 2009-10-01 01:30:52 -0700, Jokin <joaquin.castilla (AT) gmail (DOT) com> said:

You're misunderstanding the functioning of global fields in a served
environment.

The default value of globals when opened as a guest of the server is
the value that was set in them the last time the files were opened in
FM Pro. Pro, not Server.

So you set a value (say "1") in a local file, load it up onto a
server, and when a guest opens that file, they see "1" to begin with,
and can change the value at will. All other guests see the same
behavior during their sessions. One global value on a guest does not
affect any other guest, nor does it affect the server.

When a new session begins, the value begins again as the served value.

This is why any value (or graphic) uploaded during a session
disappears. You're only affecting the local value for your session.

One way to get around this is to populate all globals at launch through
a script. Keep your graphics or other values in a table, which has ONE
record, or in a table with multiple records but regular fields, not
globals. Then set the global values as each file opens. This makes it
extremely easy to determine what values a guest sees, and also makes it
easy for the developer to upgrade or change files, without worrying
about changing local values and then uploading to a server.

Many developers also use this method to populate global variables on
launch for use throughout a session.

BTW, this behavior of global fields has existed since globals were
introduced. This is not new behavior.
--
Lynn Allen
--
www.semiotics.com
Member FBA
FM 10 Certified Developer

Jokin <joaquin.castilla (AT) gmail (DOT) com> writes:

You could do this but ...

If you want to change the defaults you always have to take your db offline.
For professional use it is much better to have a 'global' table for this with
only one record.

jens

--
German FileMaker Konferenz Mai 2010
http://filemaker-konferenz.com

Jokin wrote:
re: the content of the container fields

also sounds like it may be an issue of which accout created the new
gobals; if was admin, then will be seen by all, if not admin, then only
by the creating account; just in case :

<<
the problem is just in those NEW containing fields that was
has obscure implications.

"Jens Teich" <spamtrap (AT) jensteich (DOT) de> wrote

At one place I do work for I haven't been told how to get at the FileMaker
Server by the hopeless cowboys who installed the over-priced and
over-spec'ed network server. (

Instead I had to resort to creating a Startup Script that inserts the new
data into the Global Container fields every time someone opens the hosted
database ... which is fine, unless the person isn't actually connected to
ther network server itself and then FilMaker can't find the original
graphics files to insert. \

Helpfull Harry )

On Oct 1, 6:05*pm, cortical <c... (AT) corticaldat (DOT) com.au> wrote:

You don't know what you're talking about.

G

Grip wrote:
perhaps its you that doesn't know what I'm talking about.

or it may be that you couldn't make the minor interpretive step required
due to which account created the global content (cf. which account
created the global)