Comments
4 comments
-
I get that same error (10.13.2) about half of the time I export to Excel. I haven't been able to figure out why I don't get it sometimes. It's not query complexity, because it happens on very simple SELECT statements. It's also my experience that the results are correct after dismissing the error. -
Hi @Farouche & @dkusleika
Thanks for reaching out to us regarding this.
A fix for the issue you are describing was included in the latest release of SQL Prompt (v.10.13.4). This version can be downloaded directly from: https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_10.13.4.32349.exe
I hope this helps! Please do let us know if this update does not resolve this issue for you. -
Dan_J said:Hi @Farouche & @dkusleika
Thanks for reaching out to us regarding this.
A fix for the issue you are describing was included in the latest release of SQL Prompt (v.10.13.4). This version can be downloaded directly from: https://download.red-gate.com/checkforupdates/SQLPrompt/SQLPrompt_10.13.4.32349.exe
I hope this helps! Please do let us know if this update does not resolve this issue for you.I'm sorry but the problem is still present in version 10.13.4.32349.
Please revert back to 10.12 function.
-
I think it is related to decimals and locale settings .
It works on export on data that do not contain decimals.
Add comment
Please sign in to leave a comment.
I have often with satisfaction used the 'Open in Excel' on resultsets in SSMS, but resently it has started(failing)
I have an very simple query returning an int and a decimal column, but when opening in Excel I get the showed error.
I cannot pinpoint exactly what is wrong, but after clicking 'Yes' it seems ok, but for large resultsets it can be difficult to be sure.
Do you have any suggestion as to what is going on here. It used to work flawlessly, and the function is very handy as it is the best way to get correct formatting in Excel.
Thanks in advance
Allan