OLE DB or ODBC error - Direct Query

[unknown917]

I have changed a table from import to Direct Query and am now getting a OLE DB or ODBC error in another table.  I have checked for type mismatch and replaced any nulls from the DQ table.  I have also cleared the caches and restarted the app trying to clear the errors.  The 2 errors are calculated columns from the DQ table.  Any thoughts on what may be causing the error?  All my other tables are native queries or from excel spreadsheets.  The table that is giving me the error is a native query table.  The strange thing is I have a 3rd calculated column that is not resulting in error in this table, which is why I thought it might be a type mismatch.

Any help is greatly appreciated!

[v-heq-msft]

Hi @unknown917 ,
According to your description, while converting one table from import mode to Direct Query mode, OLE DB or ODBC errors appear on the other table. Since these two errors are for calculated columns in Direct Query table, the first thing to consider is whether the calculated columns are created using functions that are not supported in Direct Query mode. You can check the following documentation, paying particular attention to the contents of the Remarks tab.

DAX overview - DAX | Microsoft Learn

Secondly, you mentioned that you have already performed the operation of clearing the cache, and that you can do this again in order to avoid the effects of the cache. The path is Home -> Transform data -> Data source settings -> Clear Permissions, clear your Direct Query table and then fetch and recreate the calculated columns, and you can do the same for other tables as well.

You can then scrutinize the details after the OLE DB or ODBC error, which will generally indicate which field or type of error occurred, so that you can target your solution.

Finally, regarding your suspicion that the data types don't match, you can check the following two posts, preferably in power query to check if your data matches in the data source and power bi.

Solved: With out changing any dat type----error:- OLE DB ... - Microsoft Fabric Community
Solved: OLE DB or ODBC error: Type mismatch. (Exception fr... - Microsoft Fabric Community

Best regards,
Albert He

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

[unknown917]

Thank, you @v-heq-msft - I have already tried clearing and recreating the direct query table and also recreating the calculated columns, to no resolution.  The frustration here is the OLE DB or ODBC error msg goes no further than that.  Gives no detail at as to what the detail of the error is.