Re: MS Access & foreign encoding bug

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Philippe Lang" <philippe(dot)lang(at)attiksystem(dot)ch>, <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: MS Access & foreign encoding bug
Date: 2005-07-26 07:30:15
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC94E7@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | 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 Philippe Lang
> Sent: 26 July 2005 07:13
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] MS Access & foreign encoding bug
>
> I have some more informations that may help you: the problem
> in the driver since version 209 only appears in Access when
> using a "pass-through query", a query sent directly to the
> database, just as we would type it in PGAdmin. The same
> query, but through "linked tables", is ok.
>
> I was not able to find out what in the record makes Access
> pass-through query fail, but it appears to be linked to text
> fields in the database. I have a specific record, filled with
> some multiline text, that cannot be retreived with a
> pass-through query. If I change some characters in the text,
> it works sometimes, but sometimes it still fails. If I copy
> and past the text twice in the text field, it suddenly works
> too... There is apprently no specific characters string or
> string length that bugs, weird!

Can you post pg_dump output of that record and the table it's in please?

I just tried passthrough queries in Access here, and the only problem I
get is it bleating about finding null values in non-variant column
types, which seems a little bizarre.

Regards, Dave.

Browse pgsql-odbc by date

  From Date Subject
Next Message Merlin Moncure 2005-07-26 12:23:45 Re: WHat do people think about using in production?
Previous Message Philippe Lang 2005-07-26 06:12:49 Re: MS Access & foreign encoding bug