Could the record be locked by another user or a script? That lock, however brief, would prevent the update, but you should also get an error message that it's locked unless your button's script includes set error capture [on]
If the only thing that button does is toggle that value, I'd replace it with a check box where the value in the value list is just the value 1. You can size the field so that the 1 is not visible. This does result in an empty field in place of zero, but since empty evaluates as zero, you can often work with that in FileMaker without any trouble. The exceptions being in existing finds that specify the zero value and relationships that can't match to an empty field so your mileage may vary with that suggestion.
Edit note: just noticed some nonsensical text in my suggestion on using a check box instead of a scripted button and have made the needed edits to correct that.
I did not have the checkbox that was used for displaying the value had editing in browse mode enabled on it.
It is was supposed to be disabled so the button that corresponds with it is the only thing function that triggers the change.
Thanks so much for taking the time to reply phil. I just needed a lil nudge!