Message-ID: <014601c04421$d20c39c0$330a0a0a@6014cwpza006>
From: "Adam Lang" <aalang@rutgersinsurance.com>
To: "pgsql-interfaces" <pgsql-interfaces@postgresql.org>
References: <8568FC767B4AD311AC33006097BCD3D61A26F8@woody.vale-housing.co.uk>
Subject: Re: Connecting remotely.
Date: Wed, 1 Nov 2000 11:36:00 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Well, I was mostly feeling out ideas... mainly because I don't know how to
write com objects or an OLE DB provider. :P

The 6th through the 10th I have a training course for VB and it gets into
Active X DLLs and Com objects, so naturally I was thinking of what I would
use my new found power for and I thought of that as a possibility.

As for the ole db... does anyone have an idea where to start looking for
that info?  Would it have to be written in C?  I found a company that sells
software that creates ole dbs...

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "'Adam Lang'" <aalang@rutgersinsurance.com>;
<pgsql-interfaces@postgresql.org>
Sent: Wednesday, November 01, 2000 10:32 AM
Subject: RE: [INTERFACES] Connecting remotely.


>
>
> > -----Original Message-----
> > From: Adam Lang [mailto:aalang@rutgersinsurance.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.
>
> Regards,
> Dave.