Comments
Sort by recent activity
tanya wrote:
Hi Thorsten,
Just to confirm your query, you are referring to insert snippets and not indentation of your SQL statements with Space?
Thanks,
Tanya
Project Manager
Red Gate Software Ltd
Hi Tanya,
thanks for your reply.
I mean both and the candidate list....
For example....
SELECT *
FROM
...
I start typing SELECT in Column 5 (I've inserted 4 Spaces before typing) using the Snippet SSF --- SQL-Prompt uses TAB in front of FROM
The same happens, when I press TAB right next to the * to get the complete Candidate list.
Hope this helps...
Regards,
Thorsten / comments
tanya wrote:
Hi Thorsten,
Just to confirm your query, you are referring to insert snippets and not indentation of your SQL statements with Space?
Thanks,
Tanya
Project Manager
Red Gate Software...
Strange....
ESC works perfectly on my installation....
Which version of SQL-Prompt are you using? / comments
Strange....
ESC works perfectly on my installation....
Which version of SQL-Prompt are you using?
tanya wrote:
Hi,
OMG sorry face again [image]
I should have noticed the build no. before giving all that downgrade tips!
Actually the 'double click' issue was a side-effect that was caused while handling an interference issue in SQL 2008 RC client query window and as SQL Prompt v3.8.2 was a patch release to support SQL 2008 RC users, it explains the reason for the 'double-click' issue being present in build 3.8.2.402 as well.
I can give you the v3.8 release build but it would not include SQL 2008 RC support. If you are happy with that, let me know and I will send you the v3.8 release build.
Thanks,
Tanya
Project Manager
Red Gate Software Ltd
Hi Tanya,
since I have installed SQLPrompt 3.9 I have the same problem [image] . Can you provide me with a working 3.8 ? I'm not using SQL 2008.
Thanks in advance.
Regards,
Thorsten / comments
tanya wrote:
Hi,
OMG sorry face again
I should have noticed the build no. before giving all that downgrade tips!
Actually the 'double click' issue was a side-effect that was caused while handli...
Thanks Ben,
we are really looking forward.... / comments
Thanks Ben,
we are really looking forward....
Hi,
we do not have any dependency in the database due to the complexity of our solution.
In order to use the SQL Generator we would need a way to order the generation of the data...
Is there any chance that it will be available in a future version? :roll:
Thanks,
Thorsten / comments
Hi,
we do not have any dependency in the database due to the complexity of our solution.
In order to use the SQL Generator we would need a way to order the generation of the data...
Is there any c...
Thanks for the info....
I'm looking forward for the V1.2 [image] / comments
Thanks for the info....
I'm looking forward for the V1.2
Hi,
it seems it is not included in 1.1?! Is that so? We really need to exclude some rows in nearly every table. [image] / comments
Hi,
it seems it is not included in 1.1?! Is that so? We really need to exclude some rows in nearly every table.
I have exactly the same problem. :shock: / comments
I have exactly the same problem. :shock:
Hi Mike,
I'm still getting the error message in the eventlog (every few minutes) about 40x a day... [image]
Any idea...?
I'm using SQL-Prompt 5.1.6.35 / comments
Hi Mike,
I'm still getting the error message in the eventlog (every few minutes) about 40x a day...
Any idea...?
I'm using SQL-Prompt 5.1.6.35
Hi Mike,
I'm using the most current version 5.1.4.11.
It seems everytime I start up my SSMS the error is written in the eventlog and the start of the SSMS takes awfully long. :roll: / comments
Hi Mike,
I'm using the most current version 5.1.4.11.
It seems everytime I start up my SSMS the error is written in the eventlog and the start of the SSMS takes awfully long. :roll: