As rdfield already suggested, DBD::Proxy is one way to go.
Usually when you're going to setup a database client machine, you need the database "client" software installed on the client machine first - then you install DBI and DBD::<your database>. For example if your database is MySQL, on a "client" machine, you would need to install the MySQL client software on the client machine first - then you would install DBD::mysql (DBI is required also, but is not dependent on the database client software already being installed).
With DBD::Proxy, you don't need to install the database client software on the client machine - you would access the database through DBD::Proxy. We used DBD::Proxy in a previous job and it worked fine for us to access an Oracle database - it took us a while to set it up and get it working, but once it worked it ran without problem. The one question/concern that was posed on the dbi-users mailing list at the time was a question of performance on DBD::Proxy - if you are expecting very heavy usage of the database through DBD::Proxy, you *may* experience performance problems. Our use of the database through DBD::Proxy was pretty light, and we didn't see any performance issues with it.
If I understand correctly, your database server is MS SQL on Win NT. Although I don't have any experience with it, I believe your other option would be to install DBI and DBD::ODBC on the Linux client box. I think(?) you can use that to access the MS SQL server on the WinNT box.
HTH
In reply to Re: Linux and Win NT, MS SQL Server and MS Access, Perl
by hmerrill
in thread Linux and Win NT, MS SQL Server and MS Access, Perl
by Win
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |