Forum Discussion
Helper IIOLE DB or ODBC error: Type mismatch - With no transformations done to Datatype
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.
7 Replies
- amitchandak
Super User
Kurtle , refer these and try to find the error
Kurtleamitchandak The table the is causing this issue has less than 100 rows with no errors in the date columns. I only use the deleted_at column to filter out items that have been soft deleted. These videos do not cover the OLE DB or ODBC error: Type mismatch. (Exception from HRESULT: 0x80020005 (DISP_E_TYPEMISMATCH)) error
v-zhenbw-msftCommunity Support
Hi Kurtle ,
Refer the following post, hope them help.
Make sure your column does not have different types of data.
Best regards,
Community Support Team _ zhenbw
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Kurtle
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
