Re: Witango-Talk: Dates again

[Steve Smith]

You could test the value with the <@ISDATE VALUE=""> tag and if it is not a valid date, try to break it up using a substring or tokenize tag, then piece it back together. This will only work if you either have a date that always fails in the same place (i.e. the 00 at the end) or if you are willing to create code to handle all of the possible scenarios.

Hope this helps,

Steve Smith

Oakbridge Information Solutions
Office: (519) 624-4388
GTA: (416) 606-3885
Fax: (519) 624-3353
Cell: (416) 606-3885
Email: [EMAIL PROTECTED]
Web: http://www.oakbridge.ca

On Thursday, August 14, 2003, at 12:54 AM, Roland Dumas wrote:

After making adjustments in witango.ini per Jason's findings of Y2K related issue, I create a quick builder taf hitting a mysql table.

In the table, the date is 2001-01-00

Don't ask what the 00 is for, that's the way it is in the database

witango sees it and presents as 01/00/00

If the date is complete and proper, such as 2001-01-03, it shows up as 01/03/01, correctly

What's going on here and is there something I can do to turn the malformed dates into the closest real date?, like 01/01/01 in the case above?

[OS X]

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf