I've seen this also. When I looked at debugging, Tango treated any two digit
year as it was 19XX when the query was sent to the database. So 02 was sent as
1902. The way I got around this was to always pass a 4 digit year.
Mike
Dan Stein wrote:
> I found a bug today in my code that I think might have caused dates to be
> inserted as 1902 instead of 2002. At least I hope it found it otherwise I'm
> not sure what caused it.
>
> I had an update going on to a record where the date is displayed as 8/1/02.
> The value of the update is <@ARG Course_Date> not formatting applied to the
> update.
>
> I am assuming that this update is what would cause the date to be changed to
> 1902 from 2002.
>
> I could not duplicate it here on my system (the only difference is I seem to
> have some the the FTF's applied) as opposed to theirs which just has SP1
> applied.
>
> I've changed all the date displays to %Y so the full year is displayed.
>
> I am updating a smalldatetime (data type)
> SQL 2000 Service Pack 2
>
> Dan
>
> --
> Dan Stein
> Digital Software Solutions
> 799 Evergreen Circle
> Telford PA 18969
> Land: 215-799-0192
> Mobile: 610-256-2843
> FMP, WiTango, EDI,SQL 2000
> [EMAIL PROTECTED]
> www.dss-db.com
>
> ________________________________________________________________________
> 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
