| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>, <pgsql-odbc(at)postgresql(dot)org> |
| Cc: | "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com> |
| Subject: | Re: libpq odbc: unrecognized return value from copy_and_convert_field |
| Date: | 2005-07-13 20:15:07 |
| Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC91F9@ratbert.vale-housing.co.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Merlin Moncure
> Sent: 13 July 2005 20:29
> To: pgsql-odbc(at)postgresql(dot)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 | Content-Type | Size |
|---|---|---|
| mylog_3628.zip | application/x-zip-compressed | 4.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2005-07-13 20:18:37 | Re: I tried turning on debug in a dsn less connection and get Catastrophic failure? |
| Previous Message | Merlin Moncure | 2005-07-13 19:52:24 | Re: libpq odbc: unrecognized return value from copy_and_convert_field |