I need a constant value (the number 1 mostly) on the left side of a
relation. I use a calc field with nothing but the figure 1 in it.

Now shall I set this calc field to global storage? I'm not sure what the
pros and cons are, apart from the obvious: that without global storage,
the calc field could be indexed and thus used on the right side of a
relation, and that with global storage, I can put this calc field on
every unrelated table (there's not need for either).

The Finder didn't indicate a change in the file size when I turn global
storage on or off.

One amazing thing, however: The relation with the globally stored calc
field on the left side works with a local file on my FMP 8 A, where both
tables are Filemaker tables.

On a file hosted with FMS 9 and opened with FMP 9, however, the relation
did not work until I turned global storage off. In this case, the calc
field was one of those additional field in an ESS table.

--
http://clk.ch

1) a field named 'Constant' and calculated as '1', stays at the value 1
whatever the record. So no need for it being global.

3) we often create a single record table where every field is regular ie non
global. Then each field can be 1) modified by the user (if he is allowed to)
2) used in relationships with other tables. I generally call that table
''parameters", and I use it also for value lists in any table.

Remi-Noel Menegaux <rnmenegaux at (no spam) free.fr> wrote:

1) a field named 'Constant' and calculated as '1', stays at the value 1
whatever the record. So no need for it being global.

Of course there's no need for the functionality. But are there reasons
for and against setting it to global? File size? Performance?

Remi-Noel Menegaux <rnmenegaux at (no spam) free.fr> wrote:

1) a field named 'Constant' and calculated as '1', stays at the value 1
whatever the record. So no need for it being global.

Christoph Kaufmann <clk at (no spam) tele2.ch> wrote:

Of course there's no need for the functionality. But are there reasons
for and against setting it to global? File size? Performance?

I have to answer my own question here. There actually is a need to set a
calc field with a constant value for global storage. Without global
storage, we depend on context, and a filtered value list won't work in
an unrelated table.

Christoph Kaufmann <clk at (no spam) tele2.ch> wrote:

Of course there's no need for the functionality. But are there reasons
for and against setting it to global? File size? Performance?

I have to answer my own question here. There actually is a need to set a
calc field with a constant value for global storage. Without global
storage, we depend on context, and a filtered value list won't work in
an unrelated table.