Skip site navigation (1) Skip section navigation (2)

Re: New snapshot - 08.00.0005

From: "Philippe Lang" <philippe(dot)lang(at)attiksystem(dot)ch>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>,<pgsql-odbc(at)postgresql(dot)org>
Subject: Re: New snapshot - 08.00.0005
Date: 2005-02-25 11:10:00
Message-ID: 6C0CF58A187DA5479245E0830AF84F4208053E@poweredge.attiksystem.ch (view raw or flat)
Thread:
Lists: pgsql-odbc
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 query from Access, nothing more.

-----Message d'origine-----
De : Dave Page [mailto:dpage(at)vale-housing(dot)co(dot)uk] 
Envoyé : vendredi, 25. février 2005 11:57
À : 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: 24 February 2005 16:52
> To: Dave Page; pgsql-odbc(at)postgresql(dot)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.


pgsql-odbc by date

Next:From: Dave PageDate: 2005-02-25 11:16:01
Subject: Re: New snapshot - 08.00.0005
Previous:From: Dave PageDate: 2005-02-25 10:57:18
Subject: Re: New snapshot - 08.00.0005

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group