As @AlexK. explained, the reason you're not seeing errors is because On Error Resume Next hides errors. When you use that, you're telling Access "ignore any error --- don't even mention it --- and continue at the next line."
But the INSERT statement that code builds will definitely trigger an error. You can confirm that fact if you copy the output of Debug.Print strSQL from the Immediate window, create a new query in the query designer, switch the query to SQL View, paste in the statement text and try to run it.
When you have a field name which includes a space, you must enclose it in square brackets so the db engine recognizes it as one identifier instead of two. I would also bracket Name because it's a reserved word, but I doubt it actually contributes to the problem here:
"INSERT INTO Employee ([Name], ATUUID, [Job ID], [Team ID], [Start Date], Comments)"
Beyond that, I suggest you use a temporary QueryDef based on a parameter query, supply the parameter values, and Execute it.
'On Error Resume Next '<-- leave this disabled, AT LEAST while debugging!
Dim db As DAO.Database
Dim qdf As DAO.QueryDef
Dim strSQL As String
strSQL = "INSERT INTO Employee ([Name], ATUUID, [Job ID], [Team ID], [Start Date], Comments)" & vbCrLf & _
"VALUES (pName, pATUUID, pJobID, pTeamID, pStartDate, pComments);"
Set db = CurrentDb
Set qdf = db.CreateQueryDef(vbNullString, strSQL)
With qdf
.Parameters("pName").Value = Me.Employye_Name.Value
.Parameters("pATUUID").Value = Me.ATTUID.Value
.Parameters("pJobID").Value = Me.cboFunc.Value
.Parameters("pTeamID").Value = Me.cboTeam.Value
.Parameters("pStartDate").Value = Me.Start_Date.Value
.Parameters("pComments").Value = Me.Comments.Value
.Execute dbFailOnError
End With
Debug.Print db.RecordsAffected
"(or maybe it is'--- can't remember for access.)On Error Resume Next7/10/2015is mathematical DIVISION, not a date.asdasdis a field name, not a string, blah blah blah