I would recommend not using Manual Calls Update with SQL Server
and installing the trigger I have posted. The hard coded manual
calls update does not handle out of order accounting, and is
not modifyable. For example, with a Cisco (and other NASes
lately), I always add an
AND i.AcctStatusType <= 2
To the first update in the trigger to get around the higher
values messaing things up. The trigger also has a check to
prevent older accounting records from overwriting newer
ones, which can really cause problems when you stop and
restart RadiusNT (queued packets by a Livingston are
sent in reverse chronological order, therefore the last one
received is the oldest, which means that port is not
correct).
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com