That's what I was figuring... so... is it possible to take those files,
compile them into a dll and make a postgresql-specific remote connection
library? So, say instead of referencing ADO in Visual Basic and using the
ODBC driver, merely wrap up necessary functionality of the client side
libraries? Would that be hard? (Never made a DLL before, so unsure).
Granted it breaks the idea of writing code to use on any database, but if
you are making an in-house application and have control over the database...
Also, it wouldn't help Access oriented people, but this would be used for a
bit more hard core integration, something that if you want, you shouldn't be
using Access for a front end anyway.
What are people's thoughts?
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Marko Kreen" <marko@l-t.ee>
To: "Adam Lang" <aalang@rutgersinsurance.com>
Cc: "pgsql-interfaces" <pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 01, 2000 9:50 AM
Subject: Re: [INTERFACES] Connecting remotely.
> On Wed, Nov 01, 2000 at 09:29:47AM -0500, Adam Lang wrote:
> > This may be a silly question, but how does *nix systems speak to a
remote
> > database without ODBC, like Windows?
>
> Database's client side libraries take care of that. But that
> means linking your app with some particular database library.
> e.g. PHP has php_pgsql, php_sybase... if you want your
> app to be database-agnostic, you can link it with e.g. UnixODBC,
> which should do the database-specific work.
>
> > As an example, PHP... I have Apache/PHP on one server, and the database
on
> > another. How does it do remote calls?
>
> $db = pg_connect("host=another.net port=5432 ... ");
>
> --
> marko