Thread: libpq odbc: unrecognized return value from copy_and_convert_field

libpq odbc: unrecognized return value from copy_and_convert_field

From
"Merlin Moncure"
Date:
Tried to hook up excel via the new odbc driver and got the above error.
It happens immediately after opening the dsn in data->Import External
Data->New Database Query.

logfile is attatched.

On a positive note we have an in house vb app that makes a few odbc
calls and it runs flawlessly.

Merlin

Attachment

Re: libpq odbc: unrecognized return value from copy_and_convert_field

From
"Merlin Moncure"
Date:
> Tried to hook up excel via the new odbc driver and got the above
error.
> It happens immediately after opening the dsn in data->Import External
> Data->New Database Query.
>
> logfile is attatched.
>
> On a positive note we have an in house vb app that makes a few odbc
> calls and it runs flawlessly.
>
> Merlin

It is interesting to note that I tried adding mylog("entering
copy_and_convert_field\n") call to very first line in
copy_and_convert_field function as well as all the failure points.
Nothing shows up in the log.

Merlin

Re: libpq odbc: unrecognized return value from copy_and_convert_field

From
"Dave Page"
Date:

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Merlin Moncure
> Sent: 13 July 2005 20:29
> To: pgsql-odbc@postgresql.org
> Subject: [ODBC] libpq odbc: unrecognized return value from
> copy_and_convert_field
>
> Tried to hook up excel via the new odbc driver and got the
> above error.
> It happens immediately after opening the dsn in data->Import External
> Data->New Database Query.

Confirmed.

> logfile is attatched.

Hmm, not much in that one. Mine might be more useful.

> On a positive note we have an in house vb app that makes a few odbc
> calls and it runs flawlessly.

Great. Looks quite good on one of my apps. I did get it to crash but
have yet to reproduce the problem - I'll keep trying :-)

Regards, Dave.

Attachment