You can post the page to itself (default behaviour, if you don't specify the
second page). You need to set a hidden variable so you know if you are
entering the page the first time, or if it is a postback. Sorry, classic ASP
does not support isPostBack
--
Manohar Kamath
Editor, .netWire
www.dotnetwire.com
"James Baker" <> wrote in message
news:...
> I'm getting a QueryString on a page. From this query string, I need to
> query a database, get a bunch of file names, attach them to an e-mail and
> fire it out (no problem). The problem is, I want it to happen when a user
> clicks a button.
>
> I've been using .NET for so long (this isn't a problem at all in .NET
> obviously)...that I've forgotten how to handle this. Am I going to need a
> second page to post an array of the file names to and then handle it
there?
> It just seems awfully redundant to need a second page to handle all of
this,
> but I guess it wouldn't shock me. It's been years since I've used classic
> ASP, so bear with me =).
>
>