Never mind. I figured it out. There was a virtual directory set up in IIS
with the name Scripts but pointing to a different directory, and a real
directory under the webroot named the same thing by with web sharing
off. The batch file was running with an explicit path.
Bill
On Wed, 26 Feb 2003 14:02:19 -0500, Bill Downall wrote:
>What security or other setting am I missing?
>
>I installed a javascript file in mysever\webroot\Scripts
>
>And referenced it with:
>
>[script src="<@APPFILEPATH>Scripts\myscript.js"></script>
>
>On my development server (WinNT 4.0), it worked. On the production
>server (Win2K) the file was not read, the objects and functions didn't
>exist.
>
>On the production server, I copied the js files up to the root, and
>changed the reference path in the TAF, and it worked fine.
>
>I had checked capitalization, tried the slash both ways. It always
>worked on the development server, never worked on the production
>server (until I copied it out of the Scripts directory to the web root.).
>
>A batch file in the same Scripts directory works on the production
>server from an R:Tango application.
>
>Bill
>
>
>
>
>
>_________________________________________________________
_______________
>TO UNSUBSCRIBE: send a plain text/US ASCII email to
[EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
