HAL GUMBERT AND DOUG DE STWOLINKSKA are hot on the trail with a way to update related fields in another table:
For years, we’ve had problems with Filemaker unstored Fields. Don’t get me wrong, unstored fields are great for having related data available in related FileMaker tables. However, unstored fields don’t work so well for Finds, Sorts, or Relationships.
Recently, Doug de Stwolinska and I been trying several methods to update a field in another table. Before now, we have been adding a trigger on the field on the layout which runs a script that updates the stored field in the other table. It works nicely, but if we add the field somewhere else we’re likely forget the trigger. Also, we might add a field to a layout by duplicating the field with the trigger which then causes an incorrect values to be updated. On top of that, we end up with a bit of screen flicker as we open a window off screen.
Yesterday, Doug and I found a way to do this with no triggers and no flicker but it does require a FileMaker Extension to be able to use FileMaker SQL INSERT, UPDATE, and DELETE statements. We use the BaseElements Extension which does a ton including FileMaker SQL!
For those unfamiliar with this problem,watch the video below for a better explanation of the problem and why it is necessary to use this technique in the first place (all within the first few minute of the video).
This new solution uses the free Base Elements plug in plus a new custom function to provide a fix. One note: Hal notes in the comments that there are some minor bugs to work out. Still, once fixed up, this will be a great way to fix a nagging problem.
via CampSoftware | FileMaker Related Field Updater / Storing Unstored Fields.