Line acting abnormally in For each loop in VBA code in MSAccess

Ok, so I started with a question and made a lot of code changes based on suggestions from this site and others, so I figured I should create a new question.

Even though my code is shorter and more efficient, the same problem persists; I am using a strSQL string that contains and the INSERT statement I want to execute. I have a FOR EACH loop that goes through every control on my MSAcess form (makes sure they are a textbox, dropdown or checkbox) and determines if the field has been modified. If it has, it generates a query string to log the change - and stores it in strSQL.

The problem is that the same request is being executed over and over again. I've added a DEBUG.PRINT statement before and after the line that executes the query string and the debugger shows the line is CHANGED! Yes, you read that correctly, it seems impossible, but I took screenshots.

First, my code:

Private Sub Form_BeforeUpdate(Cancel As Integer)
    Dim C As Control
    For Each C In Controls
        Select Case C.ControlType
            Case acTextBox, acComboBox, acCheckBox
                Dim strOriginalValue, strCurrentValue, strSQL As String

                strOriginalValue = IIf(IsNull(C.OldValue), "", IIf(C.OldValue = vbTrue Or C.OldValue = vbFalse, IIf(C.OldValue = vbTrue, "Yes", "No"), C.OldValue))
                strCurrentValue = IIf(IsNull(C.Value), "", IIf(C.Value = vbTrue Or C.Value = vbFalse, IIf(C.Value = vbTrue, "Yes", "No"), C.Value))

                If strOriginalValue <> strCurrentValue Then
                    strSQL = "INSERT INTO fringefestival_changes (change_time,change_admin,action_taken,user_affected,year_affected,field_affected,type_affected,old_value,new_value) VALUES (NOW(),'" & ThisUserName() & "','Edit'," & [id] & ",0,'" & C.ControlSource & "','Administrator','" & Replace(strOriginalValue, "'", "") & "','" & Replace(strCurrentValue, "'", "") & "')"
                    Debug.Print "Before: " & strSQL
                    CurrentDb.Execute strSQL, dbFailOnError
                    Debug.Print "After: " & strSQL
                End If
        End Select
    Next
End Sub

      

        
        
        
      

    

Here are the debugger results:

Before: INSERT INTO fringefestival_changes (change_time,change_admin,action_taken,user_affected,year_affected,field_affected,type_affected,old_value,new_value) VALUES (NOW(),'ajohnson','Edit',3,0,'indoor_performers_tab','Administrator','No','Yes')
After: INSERT INTO fringefestival_changes (change_time,change_admin,action_taken,user_affected,year_affected,field_affected,type_affected,old_value,new_value) VALUES (NOW(),'ajohnson','Edit',3,0,'indoor_performers_tab','Administrator','No','Yes')
Before: INSERT INTO fringefestival_changes (change_time,change_admin,action_taken,user_affected,year_affected,field_affected,type_affected,old_value,new_value) VALUES (NOW(),'ajohnson','Edit',3,0,'volunteers_tab','Administrator','No','Yes')
After: INSERT INTO fringefestival_changes (change_time,change_admin,action_taken,user_affected,year_affected,field_affected,type_affected,old_value,new_value) VALUES (NOW(),'ajohnson','Edit',3,0,'volunteers_tab','Administrator','No','Yes')

      

        
        
        
      

    

Secondly, my screenshots ... firstly the debugger: 1 and 2 and secondly the results: here - note that the debugger is also so I took two screenshots and the results have a line colored in as it has nothing to do with this problem.

Note that the only column that should be different in the above example should be "field_affected".

I'm at a complete loss, I have no idea why it prints the correct line to the debugger and does something else.

EDIT: I used DoCmd.RunSQL before using CurrentDb.Execute, but that required me to disable and re-enable warnings. Since the result was the same for both (same error), I used a one line solution instead of a three line solution.

UPDATE: Shoutout for shahkalpesh to help me figure out that the data is indeed inserted correctly, and I can see it in SQL Server Management Studio, but MS Access still displays incorrectly ... the question is why?

FINAL EDIT: Fixed by adding an identity / auto-increment integer column to the table, I suspect the lack of different field values ​​confused MSAccess (though it really has no reason) - the morale here is M $ - silly