Using them for expiration/extensions...which is what the MasterAccount's
fields do, but it isn't as useful to disable 1000 accounts based on a
MasterAccount. Now that that is out of the way, why is RadiusNT selecting
and DateAdding twice on the same fields? And, if it doesn't work right, then
why is it implemented for the MasterAccounts table but not SubAccounts?
If this is just "not up for discussion," then I'd like to add it to a
wishlist for RadiusNT because not everyone can afford the thousands of
dollars for a complete SQL system AND the money for a machine to handle it.
(These are just questions, I'm not trying to be an ass.)
>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
>DateAdd() is an RDBMS function. All of them handle month/year rollovers
I know it works correctly, I use it myself in several applications; that's
why it says 2/4/97 and not 1/4/97. I was talking about the code within
RadiusNT, but it was only a question. I wasn't talking about DateAdd
handling the rollover, mute point now.
>> I need to get this fixed soon!
>There is nothing broken.
If I skipped or missed these items (changes) in the documentation, I
On a whim I got our RadiusNT License key working, by removing one zero to
make it 24 characters. I checked, double checked, triple checked the key we
were sent...I still had to remove a zero. <-----This might help the other
person with their licensing problem.