Comments
4 comments
-
Hi @sajjan
Thanks for your post.
I just wanted to check to see if you managed to overcome this issue?
Please note that if you have a support contract you can always send us a ticket so that a support engineer can look at your issues directly.
Kind regards
Richard Lynch. -
Nope, still happening. Enterred a defect :https://productsupport.red-gate.com/hc/en-us/requests/113505
-
Hi @sajjan
Thanks for highlighting this issue.
As we discussed in the ticket, upgrading to the latest version (9.1.11.5038 - May 9th 2018) of SQL Prompt and recreating the snippet seem to have resolved the issue.
Please do let us know if it reoccurs.
Thanks! -
Root cause of the error was that I had another SSMS add-in called SSMSBoost which also had a template called "sel" , so when I typed "sel" and hit enter it was giving priority to the SSMSBoost snippet over SQL Prompt.
Deleting the snippet from SSMSBoost made it work.
Add comment
Please sign in to leave a comment.
Here is the original snippet code:
When i select the snippet using the mouse i get this (this is correct): When I select the same snippet using the ENTER key i get this:
Example:
SQL Prompt Log At Time of Snippet Typing:
System Details:
SQL Prompt version: 8.0.4.1638 and 9.0.10.4053
OS: Windows 7
SQL Server: 2014