Received: from ren.CREPSUNITED.COM (ip74.crepsunited.com [208.195.212.74] (may be forged)) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eADIB9s85213 for ; Mon, 13 Nov 2000 13:11:10 -0500 (EST) (envelope-from rsmith@crepsunited.com) Received: from neuromancer (ip96.crepsunited.com [208.195.212.96] (may be forged)) by ren.CREPSUNITED.COM (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with SMTP id NAA03742 for ; Mon, 13 Nov 2000 13:12:27 -0500 Message-ID: <008b01c04d9d$59c28b60$2101a8c6@CREPSUNITED.COM> From: "Robert Smith" To: Subject: Attempting to fix ODBC Implementation Date: Mon, 13 Nov 2000 13:12:56 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0088_01C04D73.701CFE60" 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/132 X-Sequence-Number: 168 This is a multi-part message in MIME format. ------=_NextPart_000_0088_01C04D73.701CFE60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable *sigh* I am fed up. The ODBC driver seems to be completely incompatible with MS Interdev... Yes, I know Interdev sucks...but.... that's what my company uses at the moment (a full conversion to Linux is in the works, but that won't be for some time).. so I'm stuck. Well... The seemingly-broken ODBC driver just doesn't cut it. So I've decided I'm going to try to fix it. I am just wondering if anyone would like to help, if this is already being worked on, if doing this would be very bad (too bad if it is :-), etc. etc. I'm willing to give it my best shot. It may take me a few decades to get it to work, but oh well. I'm fed up :-) Ok, thanks everyone.... Robert Smith ------=_NextPart_000_0088_01C04D73.701CFE60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
  *sigh* I am fed up. The ODBC driver seems to be completely=20 incompatible
with MS Interdev... Yes, I know Interdev sucks...but.... th= at's=20 what my
company uses at the moment (a full conversion to Linux is in the= =20 works, but
that won't be for some time).. so I'm stuck.  Well... Th= e=20 seemingly-broken
ODBC driver just doesn't cut it.  So I've decided = I'm=20 going to try to fix
it.  I am just wondering if anyone would like t= o=20 help, if this is already
being worked on, if doing this would be very ba= d=20 (too bad if it is :-), etc.
etc.  I'm willing to give it my best=20 shot.  It may take me a few decades to
get it to work, but oh well.= I'm=20 fed up :-) Ok, thanks everyone....

Robert Smith
------=_NextPart_000_0088_01C04D73.701CFE60--