Running asp's from a new folder.

Hi,
I just moved my asp scripts to a new folder, now they don't work.
I had everything in the wwwroot folder but decided to group the scripts into their own folders based on the function of the scripts.
I have a mainmenu.asp in the wwwroot that does a redirect to the appropriate folder/asp. This works. But once redirected, the asp scripts can't find one another. I can make them work by changing all the redirects, href's, and form actions to folder/whatever.asp.

Question:
Is there a way around this?

Thanks,
Al.

Quote:

---

Originally posted by Al Smith
Hi,
I just moved my asp scripts to a new folder, now they don't work.
I had everything in the wwwroot folder but decided to group the scripts into their own folders based on the function of the scripts.
I have a mainmenu.asp in the wwwroot that does a redirect to the appropriate folder/asp. This works. But once redirected, the asp scripts can't find one another. I can make them work by changing all the redirects, href's, and form actions to folder/whatever.asp.

Question:
Is there a way around this?

Thanks,
Al.

---

umm no..if you dont specify where the files are, how can they find them?

Hi,
Thanks for the reply.
I had thought that a redirect would set the "root"(?) to whatever folder that was redirected to.
Like when you redirect to a new address, everything now runs from that new address.
Al.

Is this a server side problem with your ASP or a client side problem with your HTML links?

Hi,
Server side.

What I had thought is when I did a Response.Redirect to an Asp script in a new folder, the scripts would use this folder as the root. That is any form actions or href's would look in this folder for the referenced page.
Apparently Response.Redirect doesn't change the "working directory"
It appears that I'm still running from the wwwroot folder even after a redirect.

Al.

Well, Reponse.Redirect's effect could be considered client side as the browser would ultimately resolve the URL, same as resolving links.

As I'm beginning to see.
I think I was taking Response.Redirect to literally, as in redirect all future responses to this location even when that location is simply another folder on the server.

Thanks for the reply.
Al.