Tango has a bug in it. It thinks that all varchar fields should never be longer than
255 characters, and truncates them to 255 characters. nvarchar (Unicode) fields and
Oracle's varchar fields which can be longer than 255 characters are simply not
recognized by Tango.
There is no workaround that I am aware of.
Perhaps you could convince Tango that the field is a "longvarchar" (aka
Memo/text/blob) rather than a varchar? I suppose you could do this by editing the XML
of the TAF, but I don't know if that would "stick" when the TAF is opened in the
editor.
Good luck
>At my clients they update the SQL server 2000 so they are running 8.00.534
>
>I am running 8.00.194
>
>I have long very long text field sometimes 2,000 characters that I am trying
>to update.
>
>The import of the data went fine
>
>When I do the update here it also works fine.
>
>But there it gets a Right truncate 22001 error.
>
>The column is a varchar 3000
>
>I had once had it set to text but it seemed to truncate the imports then.
>
>What can I do to make the update work.
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
