SQL ODBC driver failing for linked tables with memo field.

17 views

Skip to first unread message

Albert Kallal

unread,

Apr 23, 2026, 12:47:59 PM (yesterday) Apr 23

to mvd...@googlegroups.com

We are experiencing some ODBC driver failures with ODBC linked tables to SQL server.

The specific issue is nvarchar(max) (memo fields).

We have for a long time been using the legacy (windows default) ODBC driver for sql server

SQL Server.

Only some workstations are experiencing this failure (DAO.RecordSet, save/edit a row of data with a nvarchar(max).

Our current fix was to roll out, and start using

ODBC Driver 18 for SQL server

Have not determined if it was windows update – and it changed the SQL server driver (I don’t think so), or a office/Access channel update.

Will try to provide more info, but above is a heads up.

Given our over 200+ desktops, we decided for a fix was to simply change our FE installer to now check for and install the 18 driver. Doing so, all is well.