I discovered this with a much more complex calc, but am able to reproduce it by doing the following:

1. Create a new database file.

2. Add a field called EntryField that is a number field.

3. Add a custom function called "Series" that takes one parameter with the following definition:

In haste:

I wonder if this is like the display glitch I noticed in FM6... perhaps some of the discussion would be interesting to you...

December thread on "buggy portal behavior?"

Any function or expression that references a Get function has to be unstored. Does the "bug" still occur if the calculation is unstored?

Hi Vaugham,

i think Get( CalculationRepetitionNumber )

is the one notable exception....

Whether the field is stored or unstored changes nothing about the bug. I had thought of that, which is how I discovered that switching the stored/unstored status will allow the calc to be updated.

Chuck

FileMaker Version: Dev 7

Platform: Mac OS X Panther

This seems to have something to do with the calculation not being able to "see" that repetitions are being used inside the custom function.

Changing the CalcField to be defined as:

Series(EntryField) & Left( Extend(EntryField); 0 )

also causes the update to occur for all repetitions.

A cleaner one that fixes the problem is:

Series(Extend(EntryField))

and then the Extend() is not needed inside the custom function either.