Forum Discussion
OLE DB or ODBC error: Type mismatch - With no transformations done to Datatype
- 6 years ago
Yes, this problem was solved after a week and a half of back and forth with support. There were 2 cell values that were causing this issue. Instead of 2020 the cell had 2020 (10). Not sure why the quary wasn't returned with errors instead of cancelling the entire refresh but they are looking into it some more.
Yes, this problem was solved after a week and a half of back and forth with support. There were 2 cell values that were causing this issue. Instead of 2020 the cell had 2020 (10). Not sure why the quary wasn't returned with errors instead of cancelling the entire refresh but they are looking into it some more.
Same situation, had 1 cell with blankspace in an all date column. Instead of returning simgle row, it cancelled the entire refresh with OLE DB or ODBC error