Comments
Sort by recent activity
Hi Philip,
We spotted this shortly after the release of 5.3.0.3 and have since corrected the behaviour.
We'll hopefully be pushing out the fix via check for updates in the near future. If you need this urgently however, then we're happy to arrange a private build for you. Please let us know if you'd like this.
Apologies for the inconvenience, / comments
Hi Philip,
We spotted this shortly after the release of 5.3.0.3 and have since corrected the behaviour.
We'll hopefully be pushing out the fix via check for updates in the near future. If you need ...
Hi PDinCA,
Thanks for the reply - unfortunately I've not yet been able to reproduce this here.
If it's okay I'd like to ask for a little more information. Does prompting still work at earlier points in the script - or has it stopped completely? Also, does this happen EVERY time you try this, or is it intermittent behaviour?
I've logged it as a bug for now, (SP-4378).
Many thanks for your time helping us track this down, and apologies for any frustration caused!
James / comments
Hi PDinCA,
Thanks for the reply - unfortunately I've not yet been able to reproduce this here.
If it's okay I'd like to ask for a little more information. Does prompting still work at earlier point...
Hi Chris,
Thanks for the feedback - and sorry to hear Prompt's not playing nicely!
If you could PM me the error details, that'd be really useful.
Additionally - could you also include the version of the Analysis/Reporting servers you're trying to connect to, and any other SSMS add-ins (Red-Gate or otherwise) installed on the machine (such as our SQL Search).
Thanks again, / comments
Hi Chris,
Thanks for the feedback - and sorry to hear Prompt's not playing nicely!
If you could PM me the error details, that'd be really useful.
Additionally - could you also include the version o...
Hi Paul,
This has now been corrected, you should see the fix in the next release of SQL Prompt.
Many apologies for being a source of irritation in your day, and thanks for letting us know! [image] / comments
Hi Paul,
This has now been corrected, you should see the fix in the next release of SQL Prompt.
Many apologies for being a source of irritation in your day, and thanks for letting us know!
Hi Mike,
These appear to be unhandled exceptions from another addin (possibly the CodeSmith 6 beta you mentioned?). Although they're being caught by our log service, Sql Prompt isn't the cause. We record all unhandled exceptions from the AppDomain in our logs, which can be misleading, as it includes those thrown by other addins.
Hope this information helps you track the cause! / comments
Hi Mike,
These appear to be unhandled exceptions from another addin (possibly the CodeSmith 6 beta you mentioned?). Although they're being caught by our log service, Sql Prompt isn't the cause. We...
Thanks for log file - we've just come to the same conclusion regarding tabs opened with TabMagic ourselves. I would imagine this would also affect SQL documents opened directly from windows explorer into a fresh instance of SSMS.
Working on a fix! / comments
Thanks for log file - we've just come to the same conclusion regarding tabs opened with TabMagic ourselves. I would imagine this would also affect SQL documents opened directly from windows explore...