A few people have already asked me about this and posted about it in the forums, so heads up for my fellow Access developers:

Daniel Pineault just posted an important warning about a breaking issue in the latest Microsoft Office build 2604, released April 21. I've also been seeing chatter about this in several Access groups and email threads, so this one is definitely making the rounds.

The issue appears to affect Access databases connected to SQL Server via ODBC. Users are reporting failures when inserting or updating records in linked tables, often throwing errors like "Incorrect syntax near '='" or runtime error 3155. From what's being discussed, the problem may be tied to Long Text fields or nvarchar(max) columns.

There are a few possible workarounds floating around, including rolling back to build 2603 or upgrading to ODBC Driver 18. Bottom line: if you're running production systems, this is another reminder that the Current Channel can bite you. Stability still matters. This is why I don't always upgrade to the latest build right away. And if I do, I do it on ONE MACHINE first.

I'll keep an eye on this as more information comes out. In the meantime, proceed with caution if you're updating Office.

LLAP
RR