Chuck Posted April 13, 2004 Share Posted April 13, 2004 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: Link to comment Share on other sites More sharing options...
ESpringer Posted April 13, 2004 Share Posted April 13, 2004 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?" Link to comment Share on other sites More sharing options...
Vaughan Posted April 13, 2004 Share Posted April 13, 2004 Any function or expression that references a Get function has to be unstored. Does the "bug" still occur if the calculation is unstored? Link to comment Share on other sites More sharing options...
cjaeger Posted April 13, 2004 Share Posted April 13, 2004 Hi Vaugham, i think Get( CalculationRepetitionNumber ) is the one notable exception.... Link to comment Share on other sites More sharing options...
Chuck Posted April 14, 2004 Author Share Posted April 14, 2004 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 Link to comment Share on other sites More sharing options...
The Shadow Posted April 18, 2004 Share Posted April 18, 2004 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. Link to comment Share on other sites More sharing options...
The Shadow Posted April 19, 2004 Share Posted April 19, 2004 A cleaner one that fixes the problem is: Series(Extend(EntryField)) and then the Extend() is not needed inside the custom function either. Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 7312 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now