Folks, thanks for the suggestions.
It turned out it WAS importing the data anyway. I found several copies of it in the table after transferring data via a jet version of the table. We then remembered we get this with SQL back ends, and last year, just ignored the invalid argument error...