OK, in a multi-user setup, a calculation field based on a status function will act like a global field and produce a different value for each user on the network.

Correct?

-DB

Stored or unstored calc field? If it's a stored calculation, I believe it will recalc and update that field in the server copy of any record that you go into, after you exit from it.

So in other words, if I keep the indexing/storage off, it should be okay....

I don't see why something like "Status(CurrentFoundCount)" wouldn't be flexible enough to produce a different result for each user on a network. I'm just looking at a deadline and I don't have a way to test it in my home office.

BTW, I see your from Saskatoon. You wouldn't know a singer by the name of Susan Bond, would you?

Just wondering,

DB

I guess it depends what you want to do with the calculation. I wouldn't spend a lot of time setting things up without testing it first. You should never assume things will work as you expect in FileMaker.

Susan Bond? Dunno. What kind of music does she sing?

"You should never assume things will work as you expect in FileMaker."

--True.

To play it safe I'm going to set up a global field with a value of 1 and approach it in the spirit of "global * Status(CurrentFoundCount)"

I'd just rather not do that if it's not neccessary.

SB is a folk singer/songwriter and Saskatoonian, if that's the word.

--DB

"Saskatonian" Only one "o". Can't make things that easy.

Canadians....

A global field cannot be a calculation. A calculation field set to status (currentfoundcount) will display the same value in each record anyway.

Hey Vaughan, thanks. Your response makes me question how well I expressed myself. Here's my conundrum.

I'd like to have a field that displays a status function, eg. Status(CurrentFoundCount) on a multi-user setup. So, how do I define the field?

Can I use:

f1 = Status(CurrentFoundCount)

or must I use

g1 = Global, number (--then set g1 to 1 while in browse mode)

f1 = g1 * Status(CurrentFoundCount)

to make sure f1 displays a different value for each user and not the Status(CurrentFoundCount) on the server?

See what I mean?

--DB

just use a calc field = Status (whatever)

This calc field will take on whatever value is appropriate for each user.

Thanks, I thought that would probably work but didn't want to leave it up to chance.

--DB