In my opinion, you would not want to create an ASP page that ran for ever. The only way to do this is to either create a page that had an html refresh ever so often or ASP that looped indefinetely. Either way would require you to log on and start the process. The ASP looping would certainly cause CPU usage issues and both would be stop working if someone logged in and shut down the browser, the web server was reboot or stopped, and plenty of other system issues. You would then have to manually start it again.
As for my suggestion with scheduling IExplore, I had meant that the scheduler would kick it off at an interval and it would do it's processing and end until the next time the scheduler kick it off again. The downside to it is that when the scheduler started it, you may not be able to close the window. You could have multiple IE windows build up over time.
Really the best way is to create a VB app (or other language) and schedule it to run at the desired interval. Even creating a VB Script and run it through the WSH would be a better solution than ASP.
ASP was designed to dynamically create web pages to a user upon request.
Chris.