Both Miguel and TedPride are correct. But ponder this, is there isything in teh specifications that requires the data from the remote client to be sent in any particular order? No. So until the HTTP transaction is complete there is no way of knowing what data has actually been sent, let alone where it might be!

There is, however, a solution. Using JavaScript on the client you can have the client perform one transaction which tells the server code the filename and a second that actually runs the form upload. THis is not trivial, and if I recall correctly, requires a second action from the user and the use of a cookie to track what is coming from where (or at least some session management).

jdtoronto