This problem has been baffling me for some time (and I've avoided solving it by sticking with Tango 3.52). However, I'm now almost out of time (we must kill off our nt4 servers/domain and move ahead into the win2k/AD arena) and MUST resolve the problem or give up on Tango/Witango as a solution.
<A HREF = "<@CGI><@APPFILE>?_function=detail&sysInfo_uid1=<@COLUMN "sysInfo.newid" ENCODING=URL>&<@UserReferenceArgument>"><@COLUMN "sysInfo.newid" FORMAT="num:simple-integer"></A> The above USED to work (tango 3.52) to give integer numbers (of the form NNNNN) as the result (regardless of whether integer number is 2 digit, 3 digit or 4 digit (or more) number). NOW what happens is that numbers LESS than three digits are returned as integer numbers (N, NN or NNN) whereas numbers GREATER than three digits are returned as 1,234.00 formatted numbers. I use "newid" as the selection for records and can not select or update with what is now being returned as the UID to pull up the detail... have even resorted to BUILDING the entire query in witango and get to the same stumbling block. I have TRIED several times to figure this out and have failed miserably. Am using Microsoft ODBC drivers (v3.520.9042.0) on WinXP system with Witango Studio v 5.0.1.037. Witango server is running on Win2000 server and is v5.0.1.57. I have read but cannot comprehend the part of the witango Help section on formatting numbers. It is beyond me how something that used to be so simple (num:simple-integer) has become so obscure (num:1,2,3,4,5,6,7,8) with explanations that I can't follow to return the numbers the way I want them returned (as WHOLE UID numbers to use as selection for records). In addition to my feeling hopelessly stupid, I've managed to stump a programmer with YEARS of programming experience who also cannot figure out the formatting that we need to specify to return INTEGER WHOLE NUMBERS with no commas and no decimals for our unique ID key on which to select and update records Please note that I'm running out of time to update from v3.52 to Witango.and have observed this phenomenon with ALL my tafs which worked beautifully in v3.52 of Tango but haven't worked since (either in tango 2000 as I migrated through or in Witango 5). Humbly begging for a simple/quick fix so I won't have to throw away my old tango apps in favor of migration to some other product... Victoria E. Victoria Porter, Ph.D. Scientific Systems Core Facility, DIR, NIDCR 301-496-1622 / Building 49 - Room 1W17 http://wwwdir.nidcr.nih.gov/dirweb/cores/sscf/victoria.asp ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
