I have an access query which pulls data from one table from an asp page. There are about 2200 records in this table. When that page executes on my local server, the cpu usage shoots up to 100% for the few seconds it needs to run. When I run the EXACT same sql statement through the access database application on my computer, it makes my cpu usage only just a few percent and returns 10 times faster. I am using oledb connection (not odbc). I find this an odd thing. Any suggestions or is this what happens when you pull that many records from access through an asp page? The database isn't that large and it is only text. I just don't get it.