MS Access errors when DateAdd() encounters a NULL (saExtension). This
became an issue with 2.2, because we let the RDBMS do the math, rather
than do it all in RadiusNT. Therefore, 2.2 and higher doesn't support
the saExpireDate/saExtension. Those two fields never should be used,
anyways. If you are using them, you are probably using them in a way
they were not intended to be used.
SQL Server handles this correctly and therefore, saExpireDate/Extension
is supported with SQL Server.
> While running the debug, I also noticed in the SELECT statement the use of
> DateAdd. I hope I'm assuming correctly there is code to handle an expiration
> date of 1/25/97 and Extension of 10, so the final result from DateAdd is 2/4/97?
DateAdd() is an RDBMS function. All of them handle month/year rollovers
> I need to get this fixed soon!
There is nothing broken.
-- Dale E. Reed Jr. (firstname.lastname@example.org)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com