The ASP pages that I am creating do not expose the ADO, Server or Session objects to java script code. I get the "object expected" error whenever I execute any code that references these objects. These objects are available to the VBscript code that I am running in the same pages. I am using code from Paul Wilton's "Beginning JavaScript" book.

I assume ther must be a simple setting to correct this but it eludes me completely. Any ideas?

I have the same issue on IIS 2000 and IIS XP.

You will have this problem with any server and OS combination.

The VBScript that has access to the ADO, Server and Session objects is running on the server. When you write java script code, it's running on the client (unless you are writing ASP with javascript, or more correctly, with JScript). Once the asp page has been streamed to the browser in HTML, it's living in the context of the client browser. As far as the server is concerned, the page no longer exists. All the objects that live during the life cycle of a page (ADO/Server/Session) are only accessible to code running on the server.

Peter

Peter,
Thanks for the reply. I have been laboring under the misconception that JScript was just some Microsoft abomination that I could ignore (should have know better) and that VB and Java were treated on an equal footing in both the server and client. I went back and reviewed the documentation on the RUNAT directive with your comments in mind and think (hope) I understand the issue.