Received: from approximator.webwork.co.uk ([195.188.128.3]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f65HQaa02057 for ; Thu, 5 Jul 2001 13:26:36 -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 2AC0211B9; Thu, 5 Jul 2001 18:24:20 +0100 (BST) Message-ID: <004301c10578$0d4dc720$2780bcc3@northeast.co.uk> From: "NTB Technical Support" To: "Tom Lane" Cc: References: <000d01c1056a$00dadc20$2780bcc3@northeast.co.uk> <3419.994351105@sss.pgh.pa.us> Subject: Re: ADO and ODBC: More Date: Thu, 5 Jul 2001 18:29:31 +0100 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.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Archive-Number: 200107/31 X-Sequence-Number: 1784 > 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). I just don't fancy modifying all those hundreds of pages of code... And it works with SQL Server, so that would have to be broken in a compatible fashion! > I don't like the idea of changing what SQLColAttributes returns ... > that seems certain to break other applications. That was, my guess too. > But first, a wild stab in the dark --- what happens if you write > RS("""child beds""") = 33 > ie provide the quotes at the application level? Ah. Well. The recordset is a "collection" (like an associative array) whose contents is created by ADO from the field names of the most-recently executed query - so """child beds""" would be a non-existent member of the collection... Tim