"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
