Re: [MS_AccessPros] Access Memo Field Became ntext in SQL Server

 

Tim-

What is the error message you get from SQL Server when you try to change to nvarchar(max)?  It probably won't let you make a change like that as long as anyone has the database open.

As an alternative, you could try creating a new field in the table nvarchar(max), run an update query to copy the old field, then delete the old field and rename the new.  You will have to delete and recreate the linked table in Access to get it to recognize the new data type.

John Viescas, Author

Microsoft Access 2010 Inside Out

Microsoft Access 2007 Inside Out

Microsoft Access 2003 Inside Out

Building Microsoft Access Applications 

SQL Queries for Mere Mortals 

http://www.viescas.com/ 

(Paris, France)

On Feb 23, 2014, at 2:47 AM, <timdbui@gmail.com> <timdbui@gmail.com> wrote:

Hi, would any of you help me to solve this issue:

I put my back end on SQL Server 2012 and use Access 2010 as front end. I have no problem migrating the backend up to SQL Server. However, when I use Task, Export to send a table back down to Access, I have errors. The message was SQL Server no longer support ntext and it wants me to use nvarchar(Max). 

So when I try to change the fields in SQL server from ntext to nvarchar(max), it would not allow me to save 

To make things easier in the future so I don't have this issue, is there a way to make SQL Server to accept Access memo field as nvarchar(max)?  I notice that SQL server have no problem accepting the Access text field. If my field have 50 characters, then it becomes nvarchar(50) automatically in SQL Server.

Thanks so much in advance for your help!

Tim Bui

__._,_.___

Reply via web post

Reply to sender

Reply to group

Start a New Topic

Messages in this topic (2)

Visit Your Group

• New Members 1

• Privacy • Unsubscribe • Terms of Use

.

__,_._,___