Mouse click!

[john9210]

FM 8.5. I use calculation fields to apply background colors to fields that I want to highlight. The colors are stored in a global repeating field. A typical formula is:

Color1=GetRepitition(ColorContainerField,Case(Flag1=1,0,Flag1=0,2))

Flag1 is set by script.

The colors compute ok, but they do not appear unless I mouse click on the record outside a field. I’ve added the Refresh Window script step at the end of the script, but this has no effect.

Any suggestions on how I can eliminate the need to click with the mouse?

[Anuviel]

Um, I had a similar problem, solved it via commit record script step before refresh window step. Might be different then what you describe here.

[john9210]

Thanks for your response. I tried what you suggested, but no luck. I wonder if this is some sort of "bug". I'm surprised that FileMaker techs haven't responded.

[mr_vodka]

Its not a bug that I am aware of. Are you up to date on your patches?

Your color1 calc could just be:

Case ( NOT Flag1; ColorContainerField[2] )

[john9210]

Nope, the calculation is correct. However, I finally found that the global repeating container field used to store multiple colors was the source of the problem. I eliminated the approach of using a repeating field and switched to a less elegant method to store colors and the problem was solved. So...the message seems to be not to use a repeating, global, container field to store colors!

[mr_vodka]

Nope, the calculation is correct.

I never said that your calc was incorrect. I stated that it could be more simple.

So...the message seems to be not to use a repeating, global, container field to store colors!

I wouldn't agree with you here at all. People store colors in repeating global container fields all the time. Something in your implementation seems to be the issue.

[LaRetta]

So...the message seems to be not to use a repeating, global, container field to store colors!

Even though you couldn't get it to work, it DOES work and I would suggest sticking in there and finding out WHY so you can learn how to use these functionalities in future. Oh, so many missed opportunities and discoveries are lost because of not pushing a failure to one of two points 1) understanding WHY it will not work thus learning from a theory or 2) making it work thus learning from a principle. :wink2: