Hi everyone - I wonder if anyone else has run into this?



I have an Access 2010 table with an ODBC link to a SQL Server 2012 table.

In the SQL table, a number of fields are nvarchar(MAX).

In Access's (read-only) design view of the table, these fields show up as MEMO fields. Since one is used in a WHERE clause, Access predictably fails on a MEMO field comparison. Other nvarchar(MAX) fields appear as MEMO, too, which is why I think that nvarchar(MAX) is the culprit.

I changed the necessary field to text in the SQL database and relinked the table.
Still showing up as MEMO.

Any ideas what is going on under the hood and how to tinker with it? This problem is occurring in development. Production has older versions of SQL Server and Access that run just fine, which is what leads me to believe it might be related to updated versions.

Thanks!