Received: from sss.pgh.pa.us ([192.204.191.242])
	by postgresql.org (8.11.3/8.11.1) with ESMTP id f65IIpa25704
	for <pgsql-interfaces@postgresql.org>;
	Thu, 5 Jul 2001 14:18:51 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f65IIhJ03782;
	Thu, 5 Jul 2001 14:18:43 -0400 (EDT)
To: "NTB Technical Support" <techsupport@ntb.org.uk>
cc: pgsql-interfaces@postgresql.org
Subject: Re: ADO and ODBC: More 
In-reply-to: <004301c10578$0d4dc720$2780bcc3@northeast.co.uk> 
References: <000d01c1056a$00dadc20$2780bcc3@northeast.co.uk>
	<3419.994351105@sss.pgh.pa.us>
	<004301c10578$0d4dc720$2780bcc3@northeast.co.uk>
Comments: In-reply-to "NTB Technical Support" <techsupport@ntb.org.uk>
	message dated "Thu, 05 Jul 2001 18:29:31 +0100"
Date: Thu, 05 Jul 2001 14:18:42 -0400
Message-ID: <3779.994357122@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200107/32
X-Sequence-Number: 1785

"NTB Technical Support" <techsupport@ntb.org.uk> writes:
>> 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!

It does eh?  Hmm, that suggests that there is *some* way to make the
right thing happen.  Anyone know how Microsoft's version of
SQLColAttributes acts with such names?

			regards, tom lane