Problems with det2odbc ... is it supported?

Grant McClure ( (no email) )
Mon, 3 Mar 1997 11:28:37 -0800

I'm in the process of trying to integrate Emerald and RadiusNT. I wanted
to test both ways of logging calls, to a flat file, and right to an Emerald
database through ODBC. The later seems to work fairly well. It did hiccup
the first day for about half an hour or so where it wouldn't do any
logging. Restarting radius seemed to clean that up, but I'm wondering how
reliable using the ODBC connection is. What happens if SQLServer ever goes
down? I take it that that logging is lost.

So I'm thinking it might be better to always log to a flat file and then
bring the information into the Emerald database in batches using a tool
like det2odbc. I downloaded what must be the latest version to give it a
try. I've had quite a few problems.

First of all I tried running it so that it would talk to my SQLServer
database, Emerald. I got the following error:
Loading Dictionary...

ODBC: SQLConnet Error: [Microsoft][ODBC SQL Server Driver][SQL Server]
Login failed

I checked into the history of this mailing list and found that there were
others with similiar problems, and that det2odbc made an assumption when
connecting to SQLServer, using the same username and password that I logged
onto NT with.

The thing is I'm able to successfully odbcping that DSN with my NT username
and password. It connects fine.

Next thing I tried was connecting to the Access database that was installed
with RadiusNT. I set up the ODBC connection so that it would take the same
username and password. I was able to odbcping it succesfully, and det2odbc
connected succesfully as well. I don't know what the difference is!

Then I started having other problems. Det2odbc was trying to insert data
into the following columns in the call table:

None of them were in there in either the Access database or in the Emerald
database in SQLServer. I added them all except for the first which I
changed from NASIdentifier to NASIPAddress since it seemed to be part of
the key.

After doing this, I still get one more error which I haven't quite been
able to figure out yet. Here's the output (note that the data has been
changed; I'm not sure what is sensitive information at this point):
Loading Dictionary...
Processing Detail file...
Percent - Goods - Dups - Skips - Errors
ID,AscendNumInMultilink,NASPortDNIS,FramedProtocol,FramedAddress) VALUES
(#Feb 27

ODBC: SQLExecDirect Error:-1613:
[Microsoft][ODBC Microsoft Access 97 Driver] You can't add or change a
record because a related record is required in table 'Servers'.

So that's where I am now. Does anyone know if det2odbc is supported? Is
there a newer version that will do away with these errors? (I wouldn't say
that it's in good form to have to modify tables to get something like this
to work.) If it's not, I guess I'll go and write my own utility to do it.

Thanks in advance for any help, suggestions, etc.

Grant McClure