Results 1 to 5 of 5
  1. #1
    Join Date
    Apr 2002
    Posts
    2

    Unanswered: Problem linking Access97 --> SQL SERVER containing NTEXT fields

    I have a table in SQL Server 2000 that has a field in it of type "ntext". When I try to link to this table through ODBC using Access97 all that appears for each field in some of the rows is "#Error".

    When trying to edit, or even just view the data in these rows the
    following error message appears:

    "The field is too small to accept the amount of data you attempted to add.

    Try inserting or pasting less data." Design view of the linked table in Access shows that the ntext field in SQL Server was mapped as a "Text" field in Access with a field size of 255.

    Accoring to Microsoft, the "NTEXT" data type in SQL Server should be mapped to the "MEMO" data type in Access.

    It turns out that the rows that can't be viewed in Access are the ones that hold more that 255 characters in this field.

    Is there any way round this problem?
    I am using Access 97 SR2 and SQL Server 2000"

    Originally my table was upsized to SQL Server from Access97.
    Was converted automatically from "MEMO" to "NTEXT" during this process.

    I've also tried to change the datatype in SQL Server from "NTEXT" to...
    "TEXT", "NVARCHAR", "VARCHAR" and "IMAGE".
    Same result... Access97 think these are all "TEXT" fields ?

    Does anyone have a solution for this problem ?

    Sincerly BlackBee

  2. #2
    Join Date
    Aug 2004
    Posts
    5
    I have an identical problem !!

    did you solve it?? in which way?

    can you help me!!

    thanks in advance

  3. #3
    Join Date
    Aug 2004
    Posts
    5

    Problem linking Access97 --> SQL SERVER containing NTEXT fields

    HI!
    I have an identical problem (Problem linking Access97 --> SQL SERVER containing NTEXT fields )..

    did you solve it?? in which way?

    can you help me!!

    thanks in advance

    Corso

  4. #4
    Join Date
    Mar 2003
    Posts
    5

    NTEXT fields

    We modified the SQL table and truncated the text field to 255 characters.

    Not the most ideal solution, but it suited our needs.

    Tim

  5. #5
    Join Date
    Aug 2004
    Posts
    5

    solution

    The best solution is change access version!?!?
    No problem witch access2000.

    bye
    thanks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •