ODBC Connection Pooling in Access 2002

[Marc@QMI]

I posted a question yesterday about Access 2002 performance being
greatly deteriorated vs Access 97 when opening a form (with
subforms)... populated by SQL Server tables via ODBC.

I have a clearer picture now. When I test opening tables in the
database window, 97 vs 2002 versions of the same application, I
discover that ...

1) In Access 97, the first table takes a couple of seconds... but then
each additional table I open, opens lightning fast. I believe this
speed reflects connection pooling in my ODBC DSN (connection pooling
set to 60).

2) In Access 2002, *every* table takes several seconds to open with
the same ODBC DSN. It is very slow. In other words, it appears that
connection pooling is not working in an Access 2002 mdb.

Why is this? Why would opening a simple table differ so much between
the two versions of Access?

Thanks for any help.

Marc Glassgold

 

[Dirk Goldgar]

I posted a question yesterday about Access 2002 performance being
greatly deteriorated vs Access 97 when opening a form (with
subforms)... populated by SQL Server tables via ODBC.

I have a clearer picture now. When I test opening tables in the
database window, 97 vs 2002 versions of the same application, I
discover that ...

1) In Access 97, the first table takes a couple of seconds... but then
each additional table I open, opens lightning fast. I believe this
speed reflects connection pooling in my ODBC DSN (connection pooling
set to 60).

2) In Access 2002, *every* table takes several seconds to open with
the same ODBC DSN. It is very slow. In other words, it appears that
connection pooling is not working in an Access 2002 mdb.

Why is this? Why would opening a simple table differ so much between
the two versions of Access?

Thanks for any help.

Marc Glassgold

Have a look at Tony Toews' Access Performance FAQ page:

http://www.granite.ab.ca/access/performancefaq.htm

I suspect you're experiencing the LDB locking problem.