Re: Y2K and Radius: maExpireDate above 12-31-1999 (year 2000) produces login failures

Dale E. Reed Jr. ( (no email) )
Sat, 25 Jul 1998 15:23:16 -0700

Mike Stankavich wrote:
> What about the SQL Server default behavior of converting 2-digit years
> between 00 and 49 to 2000-2049 and 50-99 to 1950-1999? That would explain
> why 2050 didn't work...

I assumed the date was actually checked in SQL Server on the 2050 thing.
Its very possible that putting 1/1/50 would not actually be 1/1/2050.
We are using only the new 8 digit date formats which are mmddyyyy for
inserting dates into SQL Server that resolves the date interpratation

-- Dale E. Reed Jr.  (       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQs Internet Solutions for Today  |