Hi,
I have a similar setup, except the server is 8.3.11 / 32 bit Ubuntu
Hardy LTS. I use the 32-bit Unicode driver (version 08.04.0200) on a
64-bit Win7 laptop. I cannot reproduce the same behaviour. I'm
monitoring the connections in PgAdmin, and I see only one
connection/PID. If I open then close the linked table, the connection
persists. If I open another table, the same PID stays up. If I have
more than one table, I still see only one connection/PID. The
connection/PID is closed when I exit Access 2007. All as expected. As
far as I know, I haven't done any special modifications from the
default settings, except enable Row Versioning and Updatable Cursors
(Page 2 options).
-Mike
On 16 August 2010 12:07, Benjamin Smith <lists@benjamindsmith.com> wrote:
> Server PostgreSQL 8.4 / 64 bit
> Client MS Access 2007
> ODBC driver 8.4.200
>
> In order to support one of our clients, we've set up ODBC access to our
> database server, and the contract specifies a single ODBC database connection.
> We've enabled ODBC and gotten started, but Access seems to want to open a
> database connection for each linked table - hardly beneficial!
>
> We've tried enabling connection pooling for the PG ANSI driver (the one client
> is trying to use) to no avail - as soon as we try to set up a 2nd linked
> table, we get an error about connection limits.
>
> Is there a way to force Access (or the ODBC driver) to reuse one connection
> rather than opening multiple connections?
>
> -Ben
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
> --
> Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-odbc
>