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.
Hello, I have followed your guidelines, downloaded the OBDC driver 18 for SQL server x64. However, the problem of not inserting any new records on the SQL server still goes on. Any suggestions on how can I solve this problem?
As far as I'm aware, Microsoft is working on a fix for it right now. Are you having problems inserting records with code, or just in a form or a table directly? In the mean time what you might have to do is to INSERT just the required data. Once the record is inserted, you can come back and edit the record to add any long text fields.
Despina Karayanni
@Reply 7 months ago
Thank you very much for your prompt reply. I've actually managed to inserted 3-4 new records (as a test) with just the ordernumber field, then the program numbered the ORDERID by itself. So, I can update the orders afterwards. Hoping to find a solution soon. Thank you again.
If you are a Visitor, go ahead and post your reply as a
new comment, and we'll move it here for you
once it's approved. Be sure to use the same name and email address.
This thread is now CLOSED. If you wish to comment, start a NEW discussion in
Captain's Log.
