Received: from bush.rutgersinsurance.com (rutgersinsurance.com [38.138.71.194]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eA1EoBl60022 for ; Wed, 1 Nov 2000 09:50:11 -0500 (EST) (envelope-from aalang@rutgersinsurance.com) Received: from 6014cwpza006 ([10.10.10.51]) by bush.rutgersinsurance.com (8.9.3/8.9.3) with SMTP id JAA04480 for ; Wed, 1 Nov 2000 09:55:17 -0500 Message-ID: <010b01c04413$5fa6acc0$330a0a0a@6014cwpza006> From: "Adam Lang" Cc: "pgsql-interfaces" References: <00e801c04410$2fe0c8c0$330a0a0a@6014cwpza006> <20001101165056.A16297@l-t.ee> Subject: Re: Connecting remotely. Date: Wed, 1 Nov 2000 09:52:35 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200011/7 X-Sequence-Number: 40 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" To: "Adam Lang" Cc: "pgsql-interfaces" 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