Home

Excel Version 1907 [Expression.Error] This native database query isn't currently supported

%3CLINGO-SUB%20id%3D%22lingo-sub-796319%22%20slang%3D%22en-US%22%3EExcel%20Version%201907%20%5BExpression.Error%5D%20This%20native%20database%20query%20isn't%20currently%20supported%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-796319%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20file%20that%20contains%20a%20data%20connection%20that%20has%20been%20working%20for%20months.%26nbsp%3B%20It%20recently%20stopped%20working%20after%20the%201907%20update%20applied.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20anyone%20else%20experiencing%20an%20issue%3F%26nbsp%3B%20How%20might%20I%20go%20about%20determining%20what%20part%20of%20the%20native%20query%20is%20causing%20the%20issue%3F%26nbsp%3B%20I%20have%20also%20converted%20the%20query%20to%20a%20stored%20procedure%20and%20it%20doesn't%20work%20either.%26nbsp%3B%20Is%20there%20a%20way%20to%20get%20more%20detailed%20error%20information%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-796319%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EData%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExcel%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EGet%20%26amp%3B%20Transform%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Epowerquery%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-801478%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%20Version%201907%20%5BExpression.Error%5D%20This%20native%20database%20query%20isn't%20currently%20supported%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-801478%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20having%20the%20same%20issue%20Works%20on%201902%26nbsp%3Bfails%20on%26nbsp%3B%201907%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F389562%22%20target%3D%22_blank%22%3E%40TheCriticalPath%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-802588%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%20Version%201907%20%5BExpression.Error%5D%20This%20native%20database%20query%20isn't%20currently%20supported%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-802588%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F389562%22%20target%3D%22_blank%22%3E%40TheCriticalPath%3C%2FA%3E%26nbsp%3BWe%20are%20having%20the%20same%20problem%2C%20though%20it%20is%20only%20with%20one%20query%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20stored%20procedure%20we%20run%20uses%20dynamic%20SQL%20as%20well%20as%20a%20linked%20server%20-%20this%20may%20be%20relevant%20so%20mentioning%20it%20in-case%20it%20helps%2C%20but%20I%20haven't%20resolved%20the%20issue%20yet%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-802607%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%20Version%201907%20%5BExpression.Error%5D%20This%20native%20database%20query%20isn't%20currently%20supported%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-802607%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F391532%22%20target%3D%22_blank%22%3E%40Fleck2019%3C%2FA%3E.%26nbsp%3B%20The%20dynamic%20query%20is%20an%20excellent%20point%20and%20is%20relevant%20in%20our%20case.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-803904%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%20Version%201907%20%5BExpression.Error%5D%20This%20native%20database%20query%20isn't%20currently%20supported%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-803904%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F389562%22%20target%3D%22_blank%22%3E%40TheCriticalPath%3C%2FA%3E.%26nbsp%3BWe%20have%20also%20come%20across%20this.%20One%20query%2C%20dynamic%20sql%20with%20a%20pivot%20table%20started%20failing%2C%20others%20in%20the%20same%20workbook%20continued%20to%20run%20fine.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20rolled%20Office%20365%20back%20from%201907%20to%201906%20and%20the%20issue%20was%20resolved.%20Waiting%20for%201908%20now%20to%20see%20if%20is%20fixed%20%3CLI-EMOJI%20id%3D%22lia_slightly-smiling-face%22%20title%3D%22%3Aslightly_smiling_face%3A%22%3E%3C%2FLI-EMOJI%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-804086%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%20Version%201907%20%5BExpression.Error%5D%20This%20native%20database%20query%20isn't%20currently%20supported%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-804086%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F389562%22%20target%3D%22_blank%22%3E%40TheCriticalPath%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20the%20time%20being%2C%20it's%20suitable%20enough%20for%20our%20purposes%20to%20have%20the%20dynamic%20query%2Fpivot%20run%20refresh%20a%20cache%20table%20hourly%20with%20a%20Drop%20if%20exists%20drop%20table%20and%20a%20SELECT%20...%20INTO%20...%20in%20a%20separate%20stored%20proc%2C%20and%20update%20the%20Excel%20report%20to%20pull%20from%20the%20cache%20table%20(it's%20not%20ideal%2C%20but%20it%20has%20fixed%20the%20issue%20for%20now)%20until%20hopefully%20a%20future%20update%20resolves%20it%20properly%20and%20we%20can%20go%20back%20to%20the%20report%20being%20live%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20the%20number%20of%20columns%20and%20types%20are%20consistent%20in%20your%20dynamic%20query%2C%20I%20have%20a%20theory%20that%20putting%20a%20SELECT%20''%2C''%2CGETDATE()%2C0%2C0%20(for%20example%2C%20with%20the%20appropriate%20types%20and%20number%20of%20columns)%20at%20the%20end%20of%20the%20stored%20proc%20may%20get%20it%20to%20work%20-%20I%20think%20the%20error%20is%20because%20it%20can't%20predict%20the%20column%20types.%20Doing%20this%20with%20the%20wrong%20number%2Ftype%20of%20columns%20(my%20dynamic%20query%20is%20not%20consistent)%20gives%20a%20different%20error%20which%20is%20why%20I%20think%20it%20may%20work%2C%20(and%20my%20assumption%20is%20only%20the%20first%20result%20set%20from%20the%20dynamic%20query%20will%20actually%20display)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20have%20a%20theory%20that%20enabling%20%22Legacy%22%20SQL%20data%20imports%20and%20putting%20in%20the%20query%20the%20old%20way%20(i.e.%20how%20excel%202007%20used%20to%20do%20it%2C%20where%20the%20query%20itself%20is%20in%20the%20properties%20pane%20instead%20of%20only%20editable%20in%20power%20query%20editor)%20would%20resolve%20the%20issue%2C%20but%20I%20couldn't%20remember%20%2F%20easily%20work%20out%20how%20to%20find%20this%20so%20haven't%20tried%20it%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-824938%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%20Version%201907%20%5BExpression.Error%5D%20This%20native%20database%20query%20isn't%20currently%20supported%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-824938%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F391532%22%20target%3D%22_blank%22%3E%40Fleck2019%3C%2FA%3E%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F392009%22%20target%3D%22_blank%22%3E%40brucebdatacom%3C%2FA%3E%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F391155%22%20target%3D%22_blank%22%3E%40sthompsonSelectSires%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20recently%20applied%20the%201908%20monthly%20update%20and%20tested%20my%20dynamic%20query%20again%20and%20it%20appears%20to%20work.%26nbsp%3B%20I%20would%20like%20to%20know%20if%20the%20update%20works%20in%20your%20case%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-825912%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%20Version%201907%20%5BExpression.Error%5D%20This%20native%20database%20query%20isn't%20currently%20supported%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-825912%22%20slang%3D%22en-US%22%3EYes.%20Updating%20to%201608%20has%20also%20resolved%20our%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-861343%22%20slang%3D%22en-US%22%3ERe%3A%20Excel%20Version%201907%20%5BExpression.Error%5D%20This%20native%20database%20query%20isn't%20currently%20supported%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-861343%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F389562%22%20target%3D%22_blank%22%3E%40TheCriticalPath%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnly%20just%20looked%20at%20this%20again%20-%20reverted%20my%20cache%20table%20change%2C%20and%20it%20is%20indeed%20working%20on%20the%20version%20you%20mentioned%2C%20thank%20you%20for%20the%20reminder!%3C%2FP%3E%3C%2FLINGO-BODY%3E
TheCriticalPath
New Contributor

I have a file that contains a data connection that has been working for months.  It recently stopped working after the 1907 update applied.

 

Is anyone else experiencing an issue?  How might I go about determining what part of the native query is causing the issue?  I have also converted the query to a stored procedure and it doesn't work either.  Is there a way to get more detailed error information?

8 Replies

We are having the same issue Works on 1902 fails on  1907 @TheCriticalPath 

@TheCriticalPath We are having the same problem, though it is only with one query

 

The stored procedure we run uses dynamic SQL as well as a linked server - this may be relevant so mentioning it in-case it helps, but I haven't resolved the issue yet

@Fleck2019.  The dynamic query is an excellent point and is relevant in our case.

 

 

Hi @TheCriticalPath. We have also come across this. One query, dynamic sql with a pivot table started failing, others in the same workbook continued to run fine. 

I rolled Office 365 back from 1907 to 1906 and the issue was resolved. Waiting for 1908 now to see if is fixed

 

@TheCriticalPath 

 

For the time being, it's suitable enough for our purposes to have the dynamic query/pivot run refresh a cache table hourly with a Drop if exists drop table and a SELECT ... INTO ... in a separate stored proc, and update the Excel report to pull from the cache table (it's not ideal, but it has fixed the issue for now) until hopefully a future update resolves it properly and we can go back to the report being live

 

If the number of columns and types are consistent in your dynamic query, I have a theory that putting a SELECT '','',GETDATE(),0,0 (for example, with the appropriate types and number of columns) at the end of the stored proc may get it to work - I think the error is because it can't predict the column types. Doing this with the wrong number/type of columns (my dynamic query is not consistent) gives a different error which is why I think it may work, (and my assumption is only the first result set from the dynamic query will actually display)

 

I also have a theory that enabling "Legacy" SQL data imports and putting in the query the old way (i.e. how excel 2007 used to do it, where the query itself is in the properties pane instead of only editable in power query editor) would resolve the issue, but I couldn't remember / easily work out how to find this so haven't tried it

 

 

@Fleck2019@brucebdatacom@sthompsonSelectSires 

I recently applied the 1908 monthly update and tested my dynamic query again and it appears to work.  I would like to know if the update works in your case as well.

Yes. Updating to 1608 has also resolved our issue.

@TheCriticalPath 

 

Only just looked at this again - reverted my cache table change, and it is indeed working on the version you mentioned, thank you for the reminder!

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
22 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
cntvertex in Discussions on
13 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies