Have you considered the things the inhibit messages?
https://599cd.com/blog/display-article.asp?ID=2841

dim sql as string then set the sql to your string then take a look at what is returned (SQL)  John

Both Thomas and John have some good points. You might want to turn warnings on with the DoCmd.SetWarnings. Also, take John's advice and put that SQL string in a variable first so you can message box it and take a look. Make sure everything looks good. Sometimes, what looks good when you're writing code doesn't look good when it's actually compiled into a string. That'll let you see what's going on.

Also, it shouldn't matter, but sometimes it does. Make sure you have a space after that ) close parenthesis where your field names are right at the end of the first line. Because right now you've got no space between that closed parenthesis and the word VALUES, so you're going to get

...)VALUES

Usually, it doesn't matter, and Access can work with that, but I've seen it cause problems just like not having a space before the word WHERE.

I had a recent experience with exactly the same result trying to insert into a connected mySQL table.  In my case, I discovered the code was perfect.  The problem was the receiving field was NULL and refused to accept the insert.  Now, whenever I create a record with DOUBLE fields, I make sure it makes those fields 0 before update.