Skip site navigation (1) Skip section navigation (2)

RE: Connecting remotely.

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'Adam Lang'" <aalang(at)rutgersinsurance(dot)com>, "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgresql(dot)org>
Subject: RE: Connecting remotely.
Date: 2000-11-01 15:32:44
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces

> -----Original Message-----
> From: Adam Lang [mailto:aalang(at)rutgersinsurance(dot)com]
> Sent: 01 November 2000 14:53
> Cc: pgsql-interfaces
> Subject: Re: [INTERFACES] Connecting remotely.
> 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).

Many before you have tried this and failed miserably!! :-)

Seriously though, I think you would be creating a horrendous amount of work
for yourself (having considered the idea for 18 months or so myself). IMHO
time would be far better spent writing an OLEDB provider for PostgreSQL (a
native one, not one using the Simple Provider interface). At least then you
can still manipulate data in recordset objects which aren't really that bad
to work with and are very useful when you attach them to a hidden data
control so you can bind other controls to them.



pgsql-interfaces by date

Next:From: Clark, JoelDate: 2000-11-01 15:35:30
Subject: RE: Connecting remotely.
Previous:From: Adam LangDate: 2000-11-01 14:52:35
Subject: Re: Connecting remotely.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group