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?
I'll try to create a small database that allows you to recreate the error. But mainly, this is simply a pass-through
queryfrom Access, nothing more.
-----Message d'origine-----
De : Dave Page [mailto:dpage@vale-housing.co.uk]
Envoyé : vendredi, 25. février 2005 11:57
À : Philippe Lang; pgsql-odbc@postgresql.org
Objet : RE: [ODBC] New snapshot - 08.00.0005
> -----Original Message-----
> From: Philippe Lang [mailto:philippe.lang@attiksystem.ch]
> Sent: 24 February 2005 16:52
> To: Dave Page; pgsql-odbc@postgresql.org
> Subject: RE: [ODBC] New snapshot - 08.00.0005
>
> Sorry if it's a bit long, but here we are:
Hmm, they are essentially identical. Iirc, you said this was in Access?
Can you provide me a simple MDB to test with please, and I'll try to recreate the error here (it'll be in Access 2K3).
Thanks, Dave.
