Thanks for the reply.
[..]
> > Radius server |Network| SQL Server
> > -------------------------------------------------|-------|-------------
> > Radiator -> DBI -> DBD:ODBC -> ODBC driver(iODB) ---------> SQL 7 Server
> >
[..]
> You have almost got it - my reading of iODBC is that it still
> needs an ODBC
> driver underneath. Have a look at this URL:
>
> http://195.153.164.12/wwwboard/messages/176.html
>
> You can also do a search on Google (which is what I did - www.google.com).
>
> Depending on what platform you are running on, you may find using
> the DBD-Proxy
> is a simpler way to go, or alternatively the Sybase client libraries and
> DBD-Sybase.
Ok, that makes sense. It looks like iODBC is out of the picture, since it
uses binary drivers (the ones I saw are only for linux), and I'm using
OpenBSD.
The next choice is DBD:proxy, which I took a short look at. The picture is
now this:
Radius server |Network| SQL Server
-----------------------------|-------|--------------------------------------
----
Radiator -> DBI -> DBD:Proxy --------> DBD:Proxy -> Windows ODBC -> SQL 7
Server
Right? If this is correct, is the DBD:Proxy daemon very intensive if I chose
to run it on the SQL server, or should it be an install and use forever type
of component?
The last choice is the Sybase client client librarys. I thougt I could use
DBD:Sybase without them, but soon figured out that I couldn't. Again, I'm on
OpenBSD, and I didn't see any source distributions for the Sybase librarys,
so that looks out of the picture.
Looks like I'll be trying to get DBD:Proxy going, regardless of whether it's
easy or not. =)
Thanks for the time..
--Doug
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
