> > >> 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
