| From: | "NTB Technical Support" <techsupport(at)ntb(dot)org(dot)uk> |
|---|---|
| To: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-interfaces(at)postgresql(dot)org> |
| Subject: | Re: ADO and ODBC: More |
| Date: | 2001-07-08 09:43:41 |
| Message-ID: | 001201c10792$799349c0$2780bcc3@northeast.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
> > >> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | markMLl.pgsql-interfaces | 2001-07-08 11:36:15 | Getting info on "Max LongVarChar" under ODBC |
| Previous Message | Steve Wampler | 2001-07-06 16:29:57 | Too much data received? |