Sticky "Object has invalid source text and cannot be saved"
Often, when editing functions, and I try to save something with invalid syntax, I will get a pop-up with "Object has invalid source text and cannot be saved" instead of the useful list of errors with line numbers. (However, the product still often red-underlines a problematic portion in these cases.)
That annoyance is separately reported here:
However, sometimes, after getting this once, every successive save will fail with that error, even after the problem has been resolved. Copying and pasting into SSMS will verify that it is correct. Then closing and re-opening the function editor window will allow me to paste it back in and save it. That is, the text which threw the "invalid source" error is valid and dbForge will allow me to save it once I re-open the window. It's like it gets stuck in a "this is bad SQL" state and won't re-evaluate until the window has been reopened. This is really annoying and is happening with increasing frequency.
I'm on the Express Edition, version 5.2.177, which the product says is the latest version.
Riley Major
shared this idea
This issue is fixed in the latest version 5.4 https://www.devart.com/dbforge/sql/studio/download.html
-
Kamil Zień
commented
After editing stored procedure body and making changes to the proc body, I cannot save them back to database
Version used is dbForge Studio Express Editioni 5.3.36 -
George
commented
Sorry, my version is the same - 5.2.177 ...
-
George
commented
I get this behaviour when I start to write comment in sql text. When I first open comment and begin to write it, TextEditor recognizes possible errors due not closed comment, which is right. Then, I finish comment and close it - and cannot save the procedure because of SQL Text error.
I copy whole text, close editor window, open it again and replace current text with copied one and save - no errors. It makes a work with SQL Editor pretty uncomfortable. And I think, it comes with last release.