I realise that this might be considered more of a database-related question but recently that forum seems pretty dead. Anyway, I am interested to know how resource pooling is handled when I access a database using ADO on top of an OLEDB provider from an ASP page. I know that OLEDB now provides the resource pooling functionality within itself -- in the past it needed to work with an ODBC 3.0 provider to enable it. I also know that if you program with ADO, it defaults to running with resource pooling turned on in whichever OLEDB provider it uses. But my question is: since a new ADO object is being created (and destroyed) each time an ASP page is loaded, then the scope of a resource/connection pool must be limited to a single ASP page, right? Somebody please clarify this for me.