Comments
Sort by recent activity
The new release's behaviour seems consistent with the 10.12.2 version. Luckily it seems that no major functionalities have been added to the recent releases affected by the export to Excel bug. Thank you for reverting the change! / comments
The new release's behaviour seems consistent with the 10.12.2 version. Luckily it seems that no major functionalities have been added to the recent releases affected by the export to Excel bug. Tha...
I definitely agree with @alphonseg: a number-typed column returned by a query should be exported in Excel as a column containing a number, especially when any version older than a month works perfectly. As I wrote on September 15, it seems to me that the original "bug" (BIGINT columns shown in exponential notation) was a simple matter of how Excel treats contents wider than the cell's width: a long text gets truncated, a "long" number gets expressed in a more compact notation / comments
I definitely agree with @alphonseg: a number-typed column returned by a query should be exported in Excel as a column containing a number, especially when any version older than a month works perfe...
[image] [image] Same issue here with version 10.12.5.30313 and DECIMAL(28, 12) fields. See attached screenshot[image] / comments
Same issue here with version 10.12.5.30313 and DECIMAL(28, 12) fields. See attached screenshot
Same issue here, solved by downgrading to the 10.12.2.28458 version. Was the "Fixed an issue where BIGINT data types were being exported to Excel in scientific notation." a real issue? It seems to me that the scientific notation was only a display issue, for long BIGINT numbers with the default Excel font and cell width. Enlarging the column showed the whole number. This works in 10.12.2.28458 [image] [image] / comments
Same issue here, solved by downgrading to the 10.12.2.28458 version.Was the "Fixed an issue where BIGINT data types were being exported to Excel in scientific notation." a real issue? It seems to m...
Hi Ben, thank you all for the quick fix. I can confirm that with version 10.6.10 the "Open in Excel" functionality is now working again. Regards, Alberto / comments
Hi Ben,thank you all for the quick fix. I can confirm that with version 10.6.10 the "Open in Excel" functionality is now working again.Regards,Alberto
mdullni1 said:
When will 10.0.2 appear as an update on my system? SSMS crashes when I try to run 'Check for Updates'.
For what I understand, you have to upgrade your "bugged" version of SQL Prompt by downloading the SQLDeveloperBundle executable file from Red Gate. Running it should update your SQL Prompt version to 1.0.2, and from then on you'll be able to check for updates directly from within SSMS. / comments
mdullni1 said:
When will 10.0.2 appear as an update on my system? SSMS crashes when I try to run 'Check for Updates'.
For what I understand, you have to upgrade your "bugged" version of SQ...
Hi @TomW, thank you for the heads-up. I upgraded SQL Prompt from a freshly downloaded SQLDeveloperBundle and now it's all working as expected. Thank you very much! / comments
Hi @TomW, thank you for the heads-up. I upgraded SQL Prompt from a freshly downloaded SQLDeveloperBundle and now it's all working as expected. Thank you very much!
I had the same issue with a fresh install of my laptop. SSMS 18.4 and the latest version of SQL Prompt 10 lead to a SSMS crash every time I tried to check for updates. I momentarily solved the issue (regarding a missing library) uninstalling SQL Prompt 10, installing the latest 9.5 version and upgrading from there. Now the "Check for updates" menu doesn't crash anything, but neither shows the usual popup with the "no available updates" message / comments
I had the same issue with a fresh install of my laptop. SSMS 18.4 and the latest version of SQL Prompt 10 lead to a SSMS crash every time I tried to check for updates. I momentarily solved the issu...