Comments
Sort by recent activity
There was another thread similar to this. As of release 10.12.6.30951 this should now be fixed. / comments
There was another thread similar to this. As of release 10.12.6.30951 this should now be fixed.
Version 10.12.6.30951 is working for me also. Thanks again for including this. This helps significantly in my workflow. It honestly would have meant that I never updated the application if it wasn't fixed which defeats the purpose of having a product on a subscription model. Thanks again! / comments
Version 10.12.6.30951 is working for me also. Thanks again for including this. This helps significantly in my workflow. It honestly would have meant that I never updated the application if it wasn'...
Just to chime in here too, I do also use this ability on a daily basis. It's disappointing to hear that there are no plans to fix this in the near future soon after switching my license from the old license method to the new subscription model license. I won't be updating SQL Prompt until I've heard that this has been fixed. There is no feature or change that would make it worth it to do the 'workaround' to export. I love this product, have used it for many years, and have been an avid champion and fan for RedGate to all those I interact with. I would beg and plea with you to reconsider the priority for addressing fixing this bug that was introduced after 10.12.2.28458. The ability to simply export to excel easily is a critical feature for me. Please reconsider addressing the issue. / comments
Just to chime in here too, I do also use this ability on a daily basis. It's disappointing to hear that there are no plans to fix this in the near future soon after switching my license from the ol...
I had the same issue with version 10.12.3.28623. Downgrading to version 10.12.2.28458 allows me to export to excel correctly again. Version 10.12.3.28623 noted that a fix with exporting BIGINT data types was changed with that version. I suspect something done with that had broken the export of decimal and int to be treated as a string in excel. For those not wanting to downgrade, exporting the results as csv still works, just adds a little more of a hassle. / comments
I had the same issue with version 10.12.3.28623. Downgrading to version 10.12.2.28458 allows me to export to excel correctly again. Version 10.12.3.28623 noted that a fix with exporting BIGINT data...
I just sent the email to you with the style, screenshot, and sample code. Hope that helps! Thanks so much for looking into this! / comments
I just sent the email to you with the style, screenshot, and sample code. Hope that helps! Thanks so much for looking into this!
I'm experiencing the same as @GregDodd with an update statement using a temp table and inner join also. It highlights the first letter of the statement with the same message of "Value cannot be null."
Using SQL Prompt v8.2.1.2603 in SSMS 13.0.16106.4 / comments
I'm experiencing the same as @GregDodd with an update statement using a temp table and inner join also. It highlights the first letter of the statement with the same message of "Value cannot be nul...