Invalid SQL Statement with Monaco in Version 2505 (Fixed)

Description

In the Current Channel version 2505 build 18827.20140 from June 3 and 18827.20150 from June 10 some perfectly valid SQL statements may generate the error message

Invalid SQL Statement; expected 'DELETE', 'INSERT', 'PROCEDURE', 'SELECT' or 'UPDATE' and it is not possible to execute or save these queries.

There have been a couple of reports:

English Answers forum, started June 5

English Answers forum, restarted June 10

German Answers forum, started June 10

LinkedIn discussion, started June 9

Microsoft Q&A, started June 16

Cause

Bug in the Monaco SQL editor.

The problem happens with queries that contain non-ASCII characters like German umlauts, accented letters, Chinese, Japanese, Hebrew, Cyrillic etc. Example:

INSERT INTO Table1

VALUES ('Müller')

triggers the error message.

INSERT INTO Table1

VALUES ('Mueller')

does not.

To get the error, you must be actively working in the Monaco SQL editor (typing/deleting 1 letter is enough), not just in design view.

Status

Microsoft released a fix for this problem in the Current Channel on June 17. The fixing update is version 2505 build 18827.20164. 

If you do not receive it automatically, you can retrieve it by choosing File – Account – Update Options – Update Now.

Workaround 1

Disabling Monaco solves the problems: go to File - Options - Current Database and clear the checkbox at Enable Monaco SQL Editor.

Workaround 2

Since the bug only occurs when a query is edited in the Monaco SQL editor, queries created exclusively in design view work properly.

Notes

a) Current Channel Preview and Beta Channel are not affected by the current problems.

b) There have been several bugs in the Monaco editor in the past that caused the same or similar error messages which have mostly been fixed. Details can be found on Colin Riddington's Monaco page under Known Issues and Fixed Issues.