The COM suggestion would definetly help...but also try this...if you're not doing it already.
Use stored procedures to generate your information, as opposed to just extracting data from a table. For queries requiring calculations, this really helps...you have Access perform the calculations itself and then your ASP just is responsible for outputting the result.
It seems kind of silly to set up an entire query just to retrieve the same info you could pull from a table, but it does make a difference.
Your Web server will note the query the first time the script fires the query and for each subsequent time after that, try to use the fatest-route method of extracting your data. Kind of like an ASP method of caching information.
In SQL Server, such methods known as stored procedures, but in Access lingo they're called both "SPs" and just "queries".
While not mind-blowing in terms of performancem, it does reduce processing load on the server and is beneficial in times of high traffic.
I've done this myself for a site I set up to tarck a local football league statistics, and it works out.
ASP.NET apparently alleviates this problem altogether in terms of performance, but this is a little gem that'll do you some good.
