Did you try to use a Trigger to do script step Refresh Window?
No I did not try a Trigger to Refresh Window. Once we found the field that was not refreshing we took screen shots and then we changed the contents in the field of one of the computers. I can't recall now which computer we tried first but I do know that the field refreshed as it should on all the computers. We could not make it get stuck again if you know what I mean. Do you think that if I included a Refresh WIndow script step in my update total script (and perhaps scattered about in other scripts and triggers) that this would prevent this from happening again?
Thanks very much for your help.
The script step Refresh Window will bring actual active data to your layout for that specific record.
Don't forget commit records:
Refresh Window [Flush Cached Join Results]
Use the last option only when absolutely necessary as it can be a performance hit in some circumstances
Also be very sure that you are all working with the same set of records and that you don't have a global field affecting the results observed.
Wow. Thanks to philmodjunk and Johan Hedman. I am impressed with the quick and thoughtful responses! I have been working with Filemaker for more years than I like to remember and cannot ever remember using these forums before. Thanks again. I have included commit records and refresh window script steps and will see if I get any reports "stuck" fields.