This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi, from June, the access sql will pop up error as below, when referencing any Chinese character as the screen shot. The exact same codes worked well in May.
To work around the defect, try to create a new query using Design View. Do not use SQL View.
Hi,
This is a known bug in the current builds of Access in the Current Channel. The responsible team at Microsoft is aware of the problem and a fix is expected to come. Meanwhile you can deactivate the Monaco SQL editor as a workaround.
You can find further information and the current state of the problem in our bug documenting AFo article
Servus
Karl
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 1%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDT%3C/text%3E%3C/svg%3E)
Hi @Xiaoyu Wang
Thank you for reaching out to the Microsoft Q&A Forum.
I understand how frustrating this issue can be — especially since the same SQL worked fine just last month. Based on the information and screenshot you shared, one possible cause might be how Access handles special or Unicode characters in queries, especially with Chinese text.
From what I can see, the quotation marks around the Chinese text might be curly quotes (“离职”) instead of straight single quotes ('离职'). This detail could sometimes cause issues in Access SQL.
You could try updating your query to use straight single quotes like this:
WHERE comments = '离职'
I've shared a possible solution based on my research. If it doesn't resolve the issue, please don't hesitate to reach back out – I'd be glad to help you look into next steps.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Karl and Luis correctly identified the problem. It's a bug in the Monaco SQL Editor. Microsoft is working on a fix. The workaround he suggested is a temporary fix, pending the release of that fix. Read more here.
Hi @Xiaoyu Wang
Is there any update from you?
If yes, please feel free to let us know.
Hi @Xiaoyu Wang
It has been a while and I am writing to see how things are going with this issue.
Have you had a chance to check the replies provided?
Any update would be appreciated.
Hi,
This problem happened to me also this month. It is due to a bug in the Monaco editor. I suggest disabling the Monaco editor (this is only a temporary fix until it is fixed by Microsoft team).
The problem occurs only when special characters such as umlauts, tilde, Chinese, among other non-ASCII characters appear in our statements.
I posted about this problem on LinkedIn and some users very kindly shed light on the issue: https://www.linkedin.com/feed/update/urn:li:activity:7337743031120355328/
If the answer is helpful, please click "Accept Answer" and kindly upvote it.
This way, everyone who has the same question will know that they can find the answer here.
Hi,
Today's update in the Current Channel contains a fix for this bug. For details see the Status section in the documenting AFo article.
Servus
Karl
