OK here was the fix I used pretty easy. Changed the field type to text which Takes many many characters I think 16000 and all I had to do was drag the update field into the taf action again so it would recognize the change in type.
There must have been a fast fix for this because it works fine on my T@K server. Dan -- Dan Stein Digital Software Solutions 799 Evergreen Circle Telford PA 18969 Land: 215-799-0192 Mobile: 610-256-2843 Fax 413-410-9682 FMP, WiTango, EDI,SQL 2000 [EMAIL PROTECTED] www.dss-db.com > From: "Mike Croft" <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > Date: Tue, 23 Jul 2002 14:01:36 -0400 > To: Multiple recipients of list witango-talk <[EMAIL PROTECTED]> > Subject: RE: Witango-Talk: [OT] SQL server update problem > > Anthony, > > Try using the DBMS Action and use the <@var> metatag to define an update > routine. > > Update <tablename> set <Fieldname>=<@sq><@var name=new_value > scope=instance><@sq> where <table_primary_key>=<@var name=table_primary_key > scope=instance> > > Beware, I always use TCFs so my scopes are instance. In a TAF change the > scope to Local (Session for Witango'ers). > > This worked for me in the past. > > Good Luck, > Mike C. > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Anthony M. Humphreys > Sent: Tuesday, July 23, 2002 1:51 PM > To: Multiple recipients of list witango-talk > Subject: RE: Witango-Talk: [OT] SQL server update problem > > > 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 > > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
