Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: ODBC escape convert error
- 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: Wed, 11 Jun 2008 12:36:17 -0700
- Message-id: <396486430806111236v49054017t1de3b395750b906@mail.gmail.com> <text/plain>
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
- References:
- ODBC escape convert error
- From: Richard Broersma
- Re: ODBC escape convert error
- From: Hiroshi Inoue
- ODBC escape convert error
- Prev by Date: Re: ODBC escape convert error
- Next by Date: Re: Access query as executed by postgres
- Previous by thread: Re: ODBC escape convert error
- Next by thread: Access query as executed by postgres
- Indexes: