Besides the good points Dan makes, you need to evaluate the backend you are using. When you start getting into the hundreds of thousands of records, no matter what you do, Access' performance will suffer, espically if you are doing joins on that table. Access is a great small to intermediate tool, but it certainly has it's limits. I have actually seen databases with over a million records, but it takes forever to do anything in them.
You may want to look at some other options, ESPECIALLY if you database is going to grow any further. SQL Server is great solution in that is not overly costly, and can handle millions of records with no problems at all.
If this is not an option, then try what Dan suggests, there is not alot you can do when you get that many records in Access aside from indexing and possibly tweaking your SQL statements.
You may have to change what or how you display your data on the .asp page. Maybe show x number of records at a time or change the filter Jim Lunde
compugeeks@hotmail.com
We all agree your theory is crazy, but is it crazy enough?