file referencing between IE and Netscape

[c0ok]

Any help anyone could provide would be great !

I am currently referencing an asp file to be displayed in a frame as such :

<FRAME SRC=&quot;C:/Inetpub/

http://wwwroot/RAM/Web/reports/CR60.asp&quot;

This works great when using IE , however in Netscape 6
I recieve a 404 error, file not found.

Is there a special way to reference the file in Netscape?

Any help would be appreciated. Thanks in advance !

 

[mwolf00]

Have you tried the relative path? Using an absolute path for an asp page is very unusual.

<FRAME SRC=&quot;../../reports/CR60.asp&quot;>


use &quot;../&quot; to go up a directory level...
Get the Best Answers! faq333-2924
Is this an asp FAQ? faq333-3048

mikewolf@tst-us.com

 

[c0ok]

Thanks for your response mwolf00.

As you suggested I used a relative path and the same results occured. I was able to view the file in Internet Explorer however I still recieve the 404 error when using Netscape navigator.

I can however view the asp file in Netscape as a standalone, by simply dragging the asp file into the navigator browser area I am able to view the file. When referenced by the frames however, the browser fails to find the file in Netscape.

Any other suggestions anyone ? Anything whatsoever would be appreciated.....

 

[EdwardMartinIII]

c0ok,

If Netscape is giving you a 404, then there are only two likely reasons:

1. You have the relative path incorrect. If the asp file is in the same directory as the HTML page, then the relative path is

<FRAME SRC=&quot;CR60.asp&quot;>

. If it is not in the directory, then you have to build your path appropriately:

src="../"

means that you go up one level,

src="./"

means it's at this level and so on.

2. You have a caps problem. IE is indiscriminate regarding caps and if you're seeing the file using IE, but not Netscape or some other non potsmoking browser, then it's very likely that your case is the issue.

<FRAME SRC=&quot;CR60.asp&quot;>

is totally not the same thing as

<FRAME SRC=&quot;cr60.asp&quot;>

or

<FRAME SRC=&quot;CR60.ASP&quot;>

.

Sorry to offer you such ordinary boring suggestions, but, well, anytime IE sees something another browser can't, I've never found it to be anything other than one of these two problems, and usually, #2.

Good luck!

Edward &quot;Cut a hole in the door. Hang a flap. Criminy, why didn't I think of this earlier?!&quot; -- inventor of the cat door