I don't see why you need ODBC. For example, we use the Perl DBI::DBD modules to
communicate over TCP/IP to our DB servers (PostgreSQL and Oracle) from NT
boxes. It seems clean, easy and tidy.
For example, a programmer here with ZERO Perl experience, bought and read the
"Learning Perl" book, installed the ActiveState Perl and the DBI::DBD modules
and wrote a deamon to query an Oracle DB and serve up the returned DNA sequences
to other machines on the network. The work from start to finish, including
learning Perl, took less than two weeks. (The deamon's job is to eliminate the
large time delay in making Oracle connections; by keeping the connections open
and using them when required, it can send out DNA sequences much faster than
individual programs making the same request.).
For more information on the Perl DBI interface, see:
http://www.symbolstone.org/technology/perl/DBI/index.html
Good Luck,
Mark
"Roderick A. Anderson" wrote:
> I'm working on a program that will run on a MS Windows platform and I
> want it to use a database (PostreSQL) on a Linux box. From the research
> I've been doing I get the impression that ODBC is the preferred, if not
> the only, method to do this. So I'm hoping someone can point me at some
> simple steps (they don't have to be too detailed) on getting a MS Windows
> application to talk to a PostgreSQL database across a network.
>
> The application is being written in perl (ActiveState) and compiled
> with perl2exe to make the installation impact (not a full perl
> installation) on the Windows systems a little lighter.
>
--
Mark Dalphin email: mdalphin@amgen.com
Mail Stop: 29-2-A phone: +1-805-447-4951 (work)
One Amgen Center Drive +1-805-375-0680 (home)
Thousand Oaks, CA 91320 fax: +1-805-499-9955 (work)