Comments
Sort by recent activity
Unfortunately it is not just a matter of adding some registry keys you also need to register a .net class as a com object (Which is what regasm does) so you really have to run regasm. I would be surprised if you don't have permission to run regasm. regasm can fail for various reasons like for example some dlls are not installed so could you past exactly what error message you get from regasm please / comments
Unfortunately it is not just a matter of adding some registry keys you also need to register a .net class as a com object (Which is what regasm does) so you really have to run regasm. I would be su...
Grenzer: you could try to run the command detailed in http://www.red-gate.com/MessageBoard/vi ... php?t=5266
This detects what version of Management Studio (It works for 2005, 2005 Express and Katmai) you are running and tries to install Prompt. If there was a problem in your installation then this will hopefully sort it out.
Lionel / comments
Grenzer: you could try to run the command detailed inhttp://www.red-gate.com/MessageBoard/vi ... php?t=5266
This detects what version of Management Studio (It works for 2005, 2005 Express and Katma...
This is definatly a bug. Unfortinatly there is no setting you can tweek to get this behaviour at the moment. Hopefully we will have a fix in SQL Prompt 3.5 / comments
This is definatly a bug. Unfortinatly there is no setting you can tweek to get this behaviour at the moment. Hopefully we will have a fix in SQL Prompt 3.5
Hi after a bit of further inverstiation I can repeat this and after asking the developer responsible for the engine it turns out that this is by design. The reason is that in the line
print'in lab_missing';
where the caret is after the t SQL Prompt thinks the caret is inside the string so doesn't do the keyword capitalisation. Not the best behaviour I know.
Lionel / comments
Hi after a bit of further inverstiation I can repeat this and after asking the developer responsible for the engine it turns out that this is by design. The reason is that in the line
print'in lab_...
Can you make sure you have SQL Prompt 3.1 as I think we fixed a few issue like this betwenn 3.0 and 3.1 / comments
Can you make sure you have SQL Prompt 3.1 as I think we fixed a few issue like this betwenn 3.0 and 3.1
No problem if you have any questions then do ask. I think I am wrong about them being part of the object explorer. Made a bad assumption [image] .
Lionel / comments
No problem if you have any questions then do ask. I think I am wrong about them being part of the object explorer. Made a bad assumption .
Lionel
Really sorry for the very late reply we have been very busy trying to get SQL Prompt 3.5 ready. The short answer is these windows have nothing to do with either SQL Prompt or SQL Refactor as I have uninstalled both and all the windows are still there.
I have done a very very quick bit of prodding and they seem to be part of the object browser but I don't have any good ideas on what they do. SQL Prompt only uses one window for the intelisense on each editor window. This window will get reused within that session. Since we use Windows forms you can tell if a window is possibly part of prompt as the window class will start with WindowsForms. Not all windows forms windows are ours as visual studio uses some windows forms internally too.
Hope that helps
Lionel / comments
Really sorry for the very late reply we have been very busy trying to get SQL Prompt 3.5 ready. The short answer is these windows have nothing to do with either SQL Prompt or SQL Refactor as I have...
You can also use the alt up and the alt down keys to jump to the next and previous differences. You might find this a bit faster than using the buttons. / comments
You can also use the alt up and the alt down keys to jump to the next and previous differences. You might find this a bit faster than using the buttons.
It is not entirly obvious in there at the moment but you can use the alt + up and alt + down keys to jump to the next and previous differences too. / comments
It is not entirly obvious in there at the moment but you can use the alt + up and alt + down keys to jump to the next and previous differences too.
Hi does QA not start at all then? If it does not do you get an error when you run it from the command line. SQL Prompt does not actually change any of the QA files at all so if you have removed SQL Prompt and rebooted your machine (Just to be sure Prompt is gone) QA will be in exactally the same state as before installing SQL Prompt. If it is still not working then some files might have got corupted when it crashed (Although that seems very unlilely). If that is the case it is probably worth checking the QA registry settings to see if there is coruption in there and if there isn't then I will try to sugest some other things. / comments
Hi does QA not start at all then? If it does not do you get an error when you run it from the command line. SQL Prompt does not actually change any of the QA files at all so if you have removed SQL...