This could be a locale issue. The problem seems to be in the ODBC
driver that causes the statement to silently fail. As you have seen,
it does work if you execute it against SQL server directly.
The mins/secs problem has been noted and corrected in a beta release.
If you are using SQL Server, you should install the trigger that is
located in the radiusnt.sql script. It includes server side
replacements for both of the problems you note above (you should then
turn the manual calls update and manual services update options off
in the RadiusNT admin).
> Another question is:
> I saw on the RadiusNT admin that has a option to "USE DIFFERENT
> ACCOUNTING DSN". I would like to know which tables are necessary to put
> on each database.
To use that feature RadiusNT assumes the database is replicated to the
authentication ODBC DSN. We are in the process of re-working the logic
so that they can be completely seperate databases.
-- 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
For more information about this list, including removal, pleasesee this URL: http://www.iea-software.com/maillist.html