SQL Complete doesn't know what current statement is sometimes

[Thenrich]

Using 6.0.101. I have alt-enter mapped to SQLComplete.ExecuteCurrentStatement.

I have a SQL statement with a definition of multiple CTEs separated by commas. For testing purposes, I enter in between a SQL statement like ;select * from customer;. Note the two semi columns before and after the statement. If I hit alt-Enter, I get syntax errors. But if I highlight the line, I can execute it.

This means SQL Complete is parsing code that comes before or after the statement. I thought semicolumns define what a statement is and SQL Complete should not be looking outside of these statement delimiters.

[alexa]

Could you please provide us the script and describe the steps to reproduce the issue in detail? A video demonstrating the issue would be also of help.

You can send a reply straight to our support system at alexaATdevartDOTcom and supportATdevartDOTcom .