Thanks for your quick response Scott. I worked my way down your list of
suggestions and herewith report the result of trying each one (and have
responded to your question as well as added some additional comments and
another question (or two) for you as well as a question for the developers).
----------
From: Scott Cadillac
Reply To: [EMAIL PROTECTED]
Sent: Monday, May 17, 2004 2:28 PM
To: [EMAIL PROTECTED]
Subject: RE: Witango-Talk: mind numbing (and LONG TERM) problem with
integer number format
Hi Victoria,
What is returned if you just do <@COLUMN "sysInfo.newid" ENCODING=NONE>?
result: same thing (incorrect format)... only numbers aren't links
any more
Are you storing your "integer" value in your database with a datatype
other
than "int" (such as a text field)?
response: integer values (newid) are stored as int in database (MS
SQL)
Have you also tried the supplied format example in the documentation, for
simple-integer?
<@COLUMN "sysInfo.newid" FORMAT="num:,,0,,,,-,">
result: this doesn't work (this is ONE of the reasons why I'm so
frustrated... believed this would work and it doesn't so guess we are
talking BUG now)
If that doesn't work (bug?), you can always do:
<@CALC EXPR='<@COLUMN "sysInfo.newid"> * 1'>
result: THIS WORKS... but now I have to figure out the equivalent
calculation to do when I do the selections ... the updates ... and
everywhere else I'm trying to use integer numbers... and I'm just not sure I
have the time or energy to devote to this vs devoting time in moving my apps
into something else that is more universally used
Additional Comments/Questions: Maybe if it's a bug... there's an update that
fixes it??? (although I've been seeing this problem since Tango 2000 and
heard something once about it being a bug in the ODBC supplied by
Microsoft... which also is up to date and I'm still out of luck for things
being simple). I had really hoped that when I finally got around to
migrating my stuff... this problem would have a ready (and SIMPLE) solution.
MAYBE the developers of Witango would like to address why <@COLUMN
"sysInfo.newid" FORMAT="num:,,0,,,,-,"> doesn't work to return integer
numbers when the number is greater than 3 digits???
Anyway, I'm now at the point where I can DISPLAY (in record list) the UID
(newid) and other integer values correctly. BUT, when I click the URL (which
IS my newid) to bring up the record detail, I get an error for any newid's
greater than three digits.
A) IF newid is < or = 3 digits... the start of app file (when in
debug mode) is as follows when clicking the newid as URL (where the URL =
http://genie.nidcr.nih.gov/taf/sscf/admin/searchCPUnew.taf?_function=detail&;
sysInfo_uid1=191%2E00&_UserReference=907FC0C752D8EEB640A907E9 )
START /taf/sscf/admin/searchCPUnew.taf Witango_Server_5
_function=detail&sysInfo_uid1=191%2E00&_UserReference=907FC0C752D8EEB640A907
E9
B) IF newid is > 3 digits and I click the newid (URL =
http://genie.nidcr.nih.gov/taf/sscf/admin/searchCPUnew.taf?_function=detail&;
sysInfo_uid1=1%2C495%2E00&_UserReference=907FC0C752D8EEB640A907E9
the start of the app file is...
START /taf/sscf/admin/searchCPUnew.taf Witango_Server_5
_function=detail&sysInfo_uid1=1%2C495%2E00&_UserReference=907FC0C752D8EEB6
40A907E9
So I obviously have more things to figure out with all of this... Tomorrow
is another day... have to don my network manager hat and go take care of
something else now.
Hope this helps. Cheers...
Scott Cadillac,
403-254-5002 ~ [EMAIL PROTECTED]
------------
XML-Extranet ~ http://xmlx.ca ~ http://forums.xmlx.ca
Well-formed Programming in C# .NET, Witango, MSIE and XML
------------
IExtranet ~ http://iextranet.ca
Witango ~ http://witango.org
EasyXSLT ~ http://easyxslt.ca
IIS Watcher ~ http://iiswatcher.ca
------------
P.O. Box 69006
RPO Bridlewood SW
Calgary, Alberta
Canada T2Y 4T9
-----Original Message-----
From: Porter, Victoria (NIH/NIDCR) [mailto:[EMAIL PROTECTED]
Sent: Monday, May 17, 2004 11:27 AM
To: '[EMAIL PROTECTED]'
Subject: Witango-Talk: mind numbing (and LONG TERM) problem
with integer number format
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
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
