July 2, 2004 at 11:15 am
I'm getting the following error when I try to convert my database from Access to SQL Server:
Insert error, column 39 ('ExecutiveDate', DBTYPE_DBTIMESTAMP), status 6: Data overflow. Invalid character value for cast specification.
I originally thought this was a result of the date being invalid. However, when I check the source, the date is a valid one. In fact, it's coming from a date field in Access as well, not a text field. I also received this error on another table in the same database, except that in that one, the date field was null. My tables are set to allow nulls, so that shouldn't be a problem.
Anybody have any ideas?
Thanks,
Matt
July 2, 2004 at 11:45 am
Nevermind, I found the problem. There were other dates within that column that were wrong, the error message just pointed to one that was correct.
Matt
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply