Comments
Sort by recent activity
I had 3.8 RC installed (forgot what version, or trial?)
Installed 3.8 by using "Check Update"
it defaults to Standard version as well as I noticed the "Layout" item greyed out
Activated it again using my Toolbelt key, and it is Pro version now / comments
I had 3.8 RC installed (forgot what version, or trial?)
Installed 3.8 by using "Check Update"
it defaults to Standard version as well as I noticed the "Layout" item greyed out
Activated it again us...
tanya wrote:
Hi,
I am glad that you both liked the object definition feature that we introduced in v3.8 [image]
And yeah, the current SQL Prompt parser gives valid intellisense only when the SQL syntax in the query window is complete and devoid of any errors. But flagging the errors is a great suggestion. I have logged this as an enhancement request that we will review and probably implement for our future versions.
Thank you for taking the time to write your thoughts.
Regards,
Tanya
You guys could do what SSMS 2008 does, red underline the incorrect syntax error, just like a spell checker
I noticed these when I used SSMS 2008 yesterday, but its IntelliSense isn't near SQL Prompt of course / comments
tanya wrote:
Hi,
I am glad that you both liked the object definition feature that we introduced in v3.8
And yeah, the current SQL Prompt parser gives valid intellisense only when the SQL syntax...
All good now
So I uninstalled SQL Prompt, SQL Refactor, SQL 2005 (inc. VS2005)
Re-install everything again – SQL 2005 (Client tools only), SP2, SQL Prompt
And voila! It works, Layout function work as well. Used it for 2 days no issue
Installed SSMS Tools today, and it still seems to work, YEH!!!!
Thanks for all the help
/ comments
All good now
So I uninstalled SQL Prompt, SQL Refactor, SQL 2005 (inc. VS2005)
Re-install everything again – SQL 2005 (Client tools only), SP2, SQL Prompt
And voila! It works, Layout function wo...
Any query gives me that error when I do Layout in 3.8RC
if someone can create a support ticket for me that's better
I have a .txt file from your Diagnostic Tool to send
It's annoying, I always run into odd cases of Layout products
another support ticket F0010024 is SSMS Tools & SQL Refactor
this one, somehow SSMS, SQL Refactor, SQL Prompt 3.6, SQL Prompt 3.8 altogether, install & uninstall, creates problem again [image]
plus, 3.8RC doesn't auto-prompt anymore unless I hit Ctrl+Space, despite it's set to auto-complete
I need a Virtual Machine image.....................
thanks, I like the product thus far / comments
Any query gives me that error when I do Layout in 3.8RC
if someone can create a support ticket for me that's better
I have a .txt file from your Diagnostic Tool to send
It's annoying, I always run ...
You mean CTRL-K, CTRL-Y for Layout in SQL Prompt?
CTRL+B, CTRL+L is for SQL Refactor
SQL Refactor "hangs" my SSMS, so I uninstalled it and don't use it anymore
for SQL Prompt, I had to uninstall EVERYTHING, re-install SQL2005, etc... to get it to work (but it was only returning exceptions instead of "crash" my SSMS) / comments
You mean CTRL-K, CTRL-Y for Layout in SQL Prompt?
CTRL+B, CTRL+L is for SQL Refactor
SQL Refactor "hangs" my SSMS, so I uninstalled it and don't use it anymore
for SQL Prompt, I had to uninstall EV...
Andras wrote:
Many thanks for all your comments. We have now added an option to add a use statement at the beginning of a script generated by SQL Compare 7. This option will be off by default.
Regards,
Andras
THANK YOU / comments
Andras wrote:
Many thanks for all your comments. We have now added an option to add a use statement at the beginning of a script generated by SQL Compare 7. This option will be off by default.
R...
I understand your logic completely
I would prefer it to be an OPTION as well instead of by default
Thanks for considering it / comments
I understand your logic completely
I would prefer it to be an OPTION as well instead of by default
Thanks for considering it
That explains it, I thought SQL Compare 7 wasn't saving the project files
Yes I did read that part on the release thread
just didn't realize 6.0 cannot read 7.0 Projects
now I have 6.0 and 7.0 Projects folder, it's fine now / comments
That explains it, I thought SQL Compare 7 wasn't saving the project files
Yes I did read that part on the release thread
just didn't realize 6.0 cannot read 7.0 Projects
now I have 6.0 and 7.0 Proj...
so is it not preferable to have a test SQL server with payroll+custom database? or like you said separate instance
that way SPs won't need to be changed / comments
so is it not preferable to have a test SQL server with payroll+custom database? or like you said separate instance
that way SPs won't need to be changed