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: New snapshot - 08.00.0005 |
Date: | 2005-03-01 14:02:00 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E472B848@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: Philippe Lang [mailto:philippe(dot)lang(at)attiksystem(dot)ch]
> Sent: 01 March 2005 10:59
> To: Dave Page; pgsql-odbc(at)postgresql(dot)org
> Subject: RE: [ODBC] New snapshot - 08.00.0005
>
> Dave,
>
> I have narrowed the search. The problem with driver > 208
> comes from the way the "text" fields are handled. That's a
> bit strange, there is a certain pattern of data in the text
> field of one single row that crashes Access. There are no
> specific characters there, and if I put the exact same data
> twice in the text field, the problem disappears! That means
> that's not a problem with a foreign unsupported character...
Odd - have you retyped the data completely? Perhaps there's some
non-visible characters there that got removed when you duplicated the
data (I assume you cut/pasted it in something).
> With driver 208, no problem, on both Windows 2000 / Access
> 2000 and Windows XP / Acces 2003.
>
> My database is encoded in LATIN1. Maybe that could be
> something important?
Can you try reloading it into an ascii db? Out of curiosity...
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | anthony.caduto | 2005-03-01 17:46:18 | Re: Using pg_dump through odbc |
Previous Message | Din Adrian | 2005-03-01 13:51:16 | Re: Using pg_dump through odbc |