>Are you checking each field state individually? I was thinking maybe using AFIELDS() and just loop through all the fields to check it's state - then it wouldn't matter if the underlying fields changed.

When I've needed this check buffer type of thing in the past it's always been with minimal number of fields, like for example a child table lookup for descriptive labels on a FK. So yeah, I just checked & the handle the fields that were potential problems. But for a more generic standard, I like the thought of AFIELDS and GETFLDSTATE much better.