Received: from approximator.webwork.co.uk ([195.188.128.3]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f689ewa24627 for ; Sun, 8 Jul 2001 05:40:58 -0400 (EDT) (envelope-from techsupport@ntb.org.uk) Received: from wslibretto (dhcp39.north-east.co.uk [195.188.128.39]) by approximator.webwork.co.uk (Postfix) with SMTP id EB536118A; Sun, 8 Jul 2001 10:38:29 +0100 (BST) Message-ID: <001201c10792$799349c0$2780bcc3@northeast.co.uk> From: "NTB Technical Support" To: "Hiroshi Inoue" , "Tom Lane" Cc: References: <000d01c1056a$00dadc20$2780bcc3@northeast.co.uk> <3419.994351105@sss.pgh.pa.us> <004301c10578$0d4dc720$2780bcc3@northeast.co.uk> <3779.994357122@sss.pgh.pa.us> <3B450464.8E52CA70@tpf.co.jp> Subject: Re: ADO and ODBC: More Date: Sun, 8 Jul 2001 10:43:41 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Archive-Number: 200107/36 X-Sequence-Number: 1789 > > >> I'd write it off as broken code in ADO, and program around it by not > > >> using column names that require quoting. Ugly answer, but it's not > > >> clear that you have an alternative (short of waiting for an ADO fix). Thanks for the various inputs - looks like this is what we'll have to do. > ADO doesn't need ODBC essentially and M$ SQL Server has > its own OLE DB provider. PostgreSQL doesn't have its OLE > DB provider implementation yet Just out of curiosity, I ran the ATL OLE DB Provider wizard in VC++ to see what might be involved in doing this; soon thought better of it.... Tim