Local Response.Redirect - NT4 vs W2K

[Al Smith]

Hi,
I have a site that consists of several asp pages. The sequence of pages depends on the user input or data returned by queries.
I'm using an NT4 server for development. The final scripts reside on a Win2K server.
The main menu of the page has href's to the directory/script that the user selects. e.g. \CloseCalls\CallEntry.asp, \DefInStock\DefInStk.asp. etc.
The above works on the Win2K. On the NT4 I have to drop the first slash to get them to work.
Also, on the NT4, once I'm in the directory I can redirect to the various asp pages with simply its name. e.g.

If Request.Form("btn")="Report Parts Used" then
   Response.Redirect("Parts.asp")
Else
   Response.Redirect("RepairText.asp")
End If

On the Win2K I have to qualify the path. e.g.

If Request.Form("btn")="Report Parts Used" then
   Response.Redirect("\CloseCalls\Parts.asp")
Else
   Response.Redirect("\CloseCalls\RepairText.asp")
End If

Question:
Is this just the nature of the beast or is there something in the IIS configuration that causes this?

Thanks,
Al.

[Godfather]

Explained

Win NT

Response.Redirect it commonly used in window NT because there was nothing else to use... If you need the application to rediect you would use meta tags (Timers) or the response object... While this object should work the same for you in Win NT and 2000 you should not use it. It does a lot of unnessary traffic with the server.

Win 2k

Microsoft came out with a better why of doing it in windows 2k (ASP 3.0). Server.Transfer("URL").

If you are going to be running on a 2k box use server.transfer.

On a different note. You should write the Response statement like so:

Response.Redirect "Page.asp"

For some reason it tends to work better.

Godfather.

[Al Smith]

Thank you for the very informative response.
And welcome to this forum.
Al.