Comments
Sort by recent activity
Hi there,
Could you post up the exact error message please? We don't officially support compatibility level 7, although it "should" work (SQL Server 7 does), however there may be some other problem occurring that is only tangentially related to the compatibility level. It would be helpful if you could post up the full error message along with any other info available in the error dialog.
Thanks,
Bart / comments
Hi there,
Could you post up the exact error message please? We don't officially support compatibility level 7, although it "should" work (SQL Server 7 does), however there may be some other problem...
Hi Damian,
Sorry to see you're having problems. How long are your scripts? You might want to try increasing the number of lines above your cursor position that SQL Prompt examines, just in case your statements are being broken up by this limit, in which case the parser may become confused.
Try going to SQL Prompt > Options, then Listed Candidates > Performance and increasing "Search a fixed number of lines from the caret" to 100 or even 200. You can increase this even further if you don't notice any negative impact on performance as you type. You could instead switch over to "Search entire batch/GO block", although I wouldn't recommend this if individual SQL batches within your scripts ever run to more than a few hundred lines.
Hope that helps.
Thanks,
Bart / comments
Hi Damian,
Sorry to see you're having problems. How long are your scripts? You might want to try increasing the number of lines above your cursor position that SQL Prompt examines, just in case you...
Hi there,
I'm not sure if this is what you're after, but you can actually modify this behaviour in the Options dialog. Go to SQL Prompt > Options, then Auto Insert > Closing Characters.
You can either disable auto-insertion of the single-quotation mark entirely (I wouldn't recommend this though) by unchecking "Single quotation mark" under "Define closing characters". You could also try unchecking the "Overtype duplicate closing characters" option.
Hope that helps.
Thanks,
Bart / comments
Hi there,
I'm not sure if this is what you're after, but you can actually modify this behaviour in the Options dialog. Go to SQL Prompt > Options, then Auto Insert > Closing Characters.
You can eit...
Hi Henrik,
Can you let us know which version of SQL Prompt you are using please? I'd also recommend trying out the 3.7 patch release: http://www.red-gate.com/messageboard/vi ... php?t=6289
Please mail support@red-gate.com directly for instructions on how to get hold of it.
Hope that helps.
Thanks,
Bart / comments
Hi Henrik,
Can you let us know which version of SQL Prompt you are using please? I'd also recommend trying out the 3.7 patch release:http://www.red-gate.com/messageboard/vi ... php?t=6289
Please ma...
Hi Thomas,
Thanks for getting back to us. It's unusual that the installer wouldn't have warned you about the missing dependency, since we do (as you suggest) check for the correct .NET framework version, along with MDAC and a bunch of other bits and bobs. It looks like there might be a bug wherein this check either erroneously passes, or silently fails on some systems. This should be fixed in a future release of the toolbelt installer.
Thanks,
Bart / comments
Hi Thomas,
Thanks for getting back to us. It's unusual that the installer wouldn't have warned you about the missing dependency, since we do (as you suggest) check for the correct .NET framework ve...
Hi there,
Thanks for the suggestion. This is certainly something we're considering for a future release.
Cheers,
Bart / comments
Hi there,
Thanks for the suggestion. This is certainly something we're considering for a future release.
Cheers,
Bart
Thanks Dave,
It sounds like it might perhaps be losing track of the USE statements (if you have any). The best thing I can suggest as a workaround is that rather than closing and reopening the file you could execute the following series of keystrokes in your editor window:
CTRL+A, CTRL+X, CTRL+V
This obviously cuts and pastes the entire file, which will be quicker for you than reopening, but the key thing is the way it looks to SQL Prompt. It will appear as if you've deleted the entire contents of the script, which you have, and pasted in an entirely new script. This will force SQL Prompt to reparse the file and should mean that it will correctly infer which database you're working with. There will obviously still be some delay whilst SQL Prompt does this.
If this doesn't work it would suggest that the file contains syntax errors (hopefully not introduced by SQL Refactor!) that are confusing SQL Prompt. To test for this you can simply try to parse the file using CTRL+F5, or the blue check mark button on the toolbar (should be next to Execute unless you've customised your toolbars).
Hope that helps.
Thanks,
Bart / comments
Thanks Dave,
It sounds like it might perhaps be losing track of the USE statements (if you have any). The best thing I can suggest as a workaround is that rather than closing and reopening the file...
Hi there,
Can you post up your example please?
Thanks,
Bart / comments
Hi there,
Can you post up your example please?
Thanks,
Bart
No worries, it's now in our issue tracking system.
Cheers,
Bart / comments
No worries, it's now in our issue tracking system.
Cheers,
Bart
Hi there,
That's a cool suggestion. Kind of like the "History" list that appears at the top of the dropdown when you type a search term into the Google toolbar you mean? We could actually make it work for all objects, not just tables.
I'll make sure it's added to the list of possible future enhancements.
Thanks,
Bart / comments
Hi there,
That's a cool suggestion. Kind of like the "History" list that appears at the top of the dropdown when you type a search term into the Google toolbar you mean? We could actually make it w...