| From: | "Richard Broersma" <richard(dot)broersma(at)gmail(dot)com> |
|---|---|
| To: | "Hiroshi Inoue" <inoue(at)tpf(dot)co(dot)jp> |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: ODBC escape convert error |
| Date: | 2008-06-11 19:36:17 |
| Message-ID: | 396486430806111236v49054017t1de3b395750b906@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
On Wed, Jun 11, 2008 at 11:49 AM, Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> wrote:
> You may have to replace '{' (ODBC escape) by '(' in the line.
>
> .CommandText = .CommandText & " WHERE { T.instrumentcode,
> T.instrumentsuff, T.area, T.loopnbr ) IS NULL;
Correct again! Everything works perfectly now!
--
Regards,
Richard Broersma Jr.
Visit the Los Angles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2008-06-11 20:28:38 | Re: Access query as executed by postgres |
| Previous Message | Richard Broersma | 2008-06-11 19:07:31 | Re: [ODBC] what gives: SELECT INVALID SELECT STATEMENT TO FORCE ODBC DRIVER TO UNPREPARED STATE |