November 13, 2008 at 7:37 am
An interesting issue I have found to do with nvarchar(max) fields in a SQL server 2005 table linked from MS Access using ODBC.
The field occassionally locks ups and cannot being unlocked for editing if if all user processes are killed on the server.
This seems to be an access problem not a SQL server problem as the field is fully editable from SQL Server Enterprise manager.
The only way I have been able to resolved this is by changing the field type to nvarchar(x) where x is a valid number between 1 and 4096.
Hopefully this helps anyone else with similar issues.
Please let me know If you have had a similar issue with nvarchar(max) and if you found another solution.
February 1, 2009 at 10:40 am
I had used SSMA to convert my database, and the Memo fields were converted as nvarchar(max) & the full data was moved over, but Access could only see the last 255 characters.
Changed them all to nvarchar(4000) and it works fine now.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply