I believe what is being discussed is how the RadiusNT process
communicates with the database. Since RadusNT uses ODBC
(this IS a feature) it is necessary to use ODBC's DSN mechanism
to make that connection to the data source.
When Dale comes in and (not using enough words, admittedly)
broaches the subject of teaching RadiusNT to communicate with
MULTIPLE databases (and the complexity of supporting multiple
DSN connections) it should not be construed to mean it isn't a
capable product in its present incarnation, nor that it isn't going to
effectively accomplish your apparent intent. What it means is that
in certain circumstances connecting that way may be a better
solution for /specific/ customer situations.