Re: 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...

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?

Thanks

Philipe Lang

-----Message d'origine-----
De : Dave Page [mailto:dpage(at)vale-housing(dot)co(dot)uk]
Envoyé : vendredi, 25. février 2005 12:16
À : Philippe Lang; pgsql-odbc(at)postgresql(dot)org
Objet : RE: [ODBC] New snapshot - 08.00.0005

> -----Original Message-----
> From: Philippe Lang [mailto:philippe(dot)lang(at)attiksystem(dot)ch]
> Sent: 25 February 2005 11:10
> To: Dave Page; pgsql-odbc(at)postgresql(dot)org
> Subject: RE: [ODBC] New snapshot - 08.00.0005
>
> Yes, this is a log when using Access 2003, but the same problem
> appears with Access 2000.
>
> I made another check: another instance of the same database, with
> different data (less data), runs fine with driver >= 209. Is there
> anything special in driver >= 209 in the way data in being retrieved?

Not that I know of.

> I'll try to create a small database that allows you to recreate the
> error. But mainly, this is simply a pass-through query from Access,
> nothing more.

Thanks - I don't really have time to learn Access right now :-)

/D