If you're storing the values for each hole why do you need to store the totals? You can get them anytime in a query.
Because golf is a fairly static game (hasn't changed much in the last 200 years) you can get away with Hole1, Hole2, Hole3, etc as fields since it will probably simplify your calculations. Make a query based on your table, with three additional fields.
Front9: Hole1+Hole2+Hole3+...+Hole9
Back9: Hole10+Hole11+...+Hole18
GameScore: Front9+Back9
Now base your form on that query, and include fields for those three fields. They'll show up automatically, never be out of date if someone scores themselves wrong (like that would ever happen), and eliminate redundant storage. Make sure you set those fields to Enabled: No, Locked: Yes so people aren't tempted to try to change the totals (they won't be able to, but it'll be cleaner that way).
Now since I already told you NOT to normalize your database in one way, I feel obligated to ask: How are you storing consecutive games for the same player in your database?