How can we help you today? How can we help you today?

Auto insert pegging processor

I tried to add the following as an auto insert

/*
CREATE DATE:
CREATED BY: Tim Goldstein
**********************************************************************************************
FUNCTION:
**********************************************************************************************
MODIFICATIONS:
Date Name Description
**********************************************************************************************
PURPOSE:
*/

It is a block that I add to my stored procedures so anyone following knows something about it and we can keep some history at it is modified. When I hit the test snippet button the option window goes crazy, my mouse cursor disappear from the screen, and my processor pegs out at 100%. To recover I have to keyboard to task manager and then kill the SQLPrompt process.

Seems to me that I should be able to add a comment block as well as any other snippet without crashing the program.

Tim
Denver, CO
tgoldstein
0

Comments

3 comments

Sort by
  • Bart Read
    Hi Tim,


    Firstly, I apologise for the delay in replying to your post. For some reason it slipped under the radar.

    SQL Prompt 2 has problems with the use of certain characters in snippets and it looks like unfortunately you've found one of these. This is due to the mechanism used by SQL Prompt 2 for making changes in the editor you're using. These issues do not affect SQL Prompt 3, which will be released sometime over the next few weeks or so. The best thing I can suggest therefore is that when it is released you upgrade to the new version.

    I hope this helps, and apologise that I can't offer you a more direct solution at this point in time.


    Kind regards,
    Bart
    Bart Read
    0
  • tgoldstein
    Bart,

    Thanks for the reply.

    I have already bought my Prompt 3 license so I am waiting anxiously for it's introduction.

    Any input on Auto Insert being case sensitive in recognizing the shortcut code when you use it, but not being case sensitive when you try to establish a shortcut? Mentioned this in a previous post regarding ssf working and SSF not working. But I can not add in SSF as an additional auto insert as the option screen thinks it is the same as ssf.

    Tim
    Denver, CO
    tgoldstein
    0
  • Bart Read
    Hi Tim,


    In version 3 it's perfectly possible to define two snippets with shortcuts differing only in case. So "ssf" and "SSF" would be permitted, although I wouldn't necessarily recommend this.

    They will always both appear on the candidate list, however unless case-sensitive filtering is used you'll find the SSF gets selected by default and you'll need to use the cursor keys to scroll down to ssf, which should be the next in the list.

    Hope that helps.


    Thanks,
    Bart
    Bart Read
    0

Add comment

Please sign in to leave a comment.