> looks like it's witango:
> What's the cure??
It is called a 4 digit year. E.g. 2003
There is no ambiguity.
If you only collect 2 digit dates try something like this:
If mydate is > 20
mydate = '19' + mydate
Else
mydate = '20' + mydate
This is only pseudo code so you will have to code it with the correct
syntax.
On 23/7/03 10:47 AM, "Roland Dumas" <[EMAIL PROTECTED]> wrote:
> looks like it's witango:
> [147]
> INSERT INTO forum (subject,author,email,date,message) VALUES (?,?,'',{
> d '1902-07-16' },?)
>
> What's the cure?? I can protect against it to a certain extent, but is
> there some config someplace that I need to deal with?
>
> On Tuesday, July 22, 2003, at 05:38 PM, Ben Johansen wrote:
>
>> Turn Debug on and view what the insert/update statement being issued
>> from Witango.
>> If you see it as 1903-01-02 in the debug then it is witango, else it is
>> mysql.
>>
>> If you are using T2k then it could be T2k.
>> Since the big fallout of y2k I got into habit of enter 2003 or 1903
>> fully. Mostly I provide a popup calendar to just click.
>>
>> Hope this helps
>>
>>
>> -----Original Message-----
>> From: Roland Dumas [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, July 22, 2003 5:28 PM
>> To: [EMAIL PROTECTED]
>> Subject: Witango-Talk: Y2K problem?
>>
>> I just created a new record taf and created an entry that is 1/2/03 in
>> a date field. I looked at the record in mysql and it was 1903-01-02.
>> Where is the Y2K problem?
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
