Access Queries vs Tables in ASP pages

[M Stery]

As a general rule, is using a stored Access query as the source for an
asp page faster than making the asp page query the table directly?
I'm looking to improve the performance of some asp pages that use an
Access 2000 db as the backend. Users can post info to the same tables
I'm querying from the asp pages, and I notice some severe slowdowns if
someone is posting data to a table simultaneously with someone viewing
info from the asp pages that's pulling data from that same table. Any
suggestions appreciated. Thanks.

[Ross Presser]

ms****@soon.com (M Stery) wrote in news:8b*************************@posting.google.co m:

As a general rule, is using a stored Access query as the source for an
asp page faster than making the asp page query the table directly?
I'm looking to improve the performance of some asp pages that use an
Access 2000 db as the backend. Users can post info to the same tables
I'm querying from the asp pages, and I notice some severe slowdowns if
someone is posting data to a table simultaneously with someone viewing
info from the asp pages that's pulling data from that same table. Any
suggestions appreciated. Thanks.

Querying the table versus a stored querydef will not (in my experience) have any effect on performance.
However, limiting the number of columns and rows returned by the query will. In the specific instance you
mention, your problem may be solvable by tweaking the recordset type or the lock modes used by the ASP
pages.

--
Ross Presser -- rpresser AT imtek DOT com
"... VB is essentially the modern equivalent of vulgar Latin in 13th Centurary Europe. Understand it, and
you can travel to places you never heard of and still understand some people." -- Alex K. Angelopoulos