Comments
Sort by recent activity
I may have skipped the last beta. From what I remember when I tried it I just added the path of the Compact db in the exclusion tab.
After I installed the release on a developer's desktop working with both Compact and Std, he complained he had to deactivate SQL Prompt. When I went to configure it the same what I had done with the beta, it seemed to me the server/db dialog was not what I had seen with the beta. There's been a couple of months between the 2 incidents, so I am not sure.
I tested the beta with SQL Compact (in november or december) and, at your suggestion, I added the exclusion path and it worked. When we installed the release we could not make it work anymore.
We've bought a bunch of serials but only a few of us work regularly with SQL Compact and that specific developer speaks a couple of languages but only 3 words of english [image] so he asked to post to the forum for him. Since he does lots of cross db queries between different versions, disabling SQL Prompt completely is not a good workaround for him.
thanks
Eric / comments
I may have skipped the last beta. From what I remember when I tried it I just added the path of the Compact db in the exclusion tab.
After I installed the release on a developer's desktop working w...
Thanks for replying so quickly.
A workaround I am using is to deactivate SQL Prompt when working in split view (I absolutely need split view sometimes). This brought a simple thought: the enable/disable could possibly be available in the toolbar which is easier to access than the menu (if you have access to adding your stuff in the toolbar of SSMS).
BTW, possibly because I haven't become familiar enough, I always prompt SQL Prompt manually with Ctr-space. The default Enter configuration was driving me mad because it was inserting stuff all the time when I was simply trying to format my code. Using Ctr-Space does not bother me but I am curious of the default behavior: what am I missing? How can we use Enter normally (I tried shift-enter and other variations but the auto-complete was always triggered)?
Thanks,
Eric / comments
Thanks for replying so quickly.
A workaround I am using is to deactivate SQL Prompt when working in split view (I absolutely need split view sometimes). This brought a simple thought: the enable/di...
Hi Bart,
Ignoring the db works. Good enough workaround. Thanks!
Eric
Happy New Year!!
[/img] / comments
Hi Bart,
Ignoring the db works. Good enough workaround. Thanks!
Eric
Happy New Year!!
[/img]