Thanks for the reply.

The article was very interesting but I'm still confused. Reading that
article, I would expect my OWC to not function without the datapump
installed on the IIS server. But our users are able to access pages with
OWC charts without any problems. The only issue is when I tried to put
an MDX command on the ASP page and try to get the cube last process
date. I really didn't see anything in the article that would explain why
one thing works and the other does not.



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

matt,
the owc really has nothing to do with the web server. the only purpose the web server holds in the case of OWC is to host the page that contains the code that runs on your local machine to start the OWC. from there, all requests to AS occur directly between your machine and the AS server, via PTS. you could even create a .htm file on your hard drive that hosts an OWC and run it from there (without any web server) and it will work.

when you run mdx in your asp, the asp code is being processed on the web server and therefore, the web server must be able to communicate/authenticate to the AS, as well as have the necessary olap objects installed, like oledb for olap.

does this make sense?
vincent

Thanks for the reply.

The article was very interesting but I'm still confused. Reading that
article, I would expect my OWC to not function without the datapump
installed on the IIS server. But our users are able to access pages with
OWC charts without any problems. The only issue is when I tried to put
an MDX command on the ASP page and try to get the cube last process
date. I really didn't see anything in the article that would explain why
one thing works and the other does not.



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Interesting. I new that the PTS was required on the client machine to
run OWC but I still assumed that the web server was still involved in
the process. From what I'm reading now, the web server kind of "steps
away" from the communication and allows the client and the AS to talk
directly (almost). If this is true, that would explain why the MDX code
doesn't work since it runs "server side" and the correct DLL's aren't
installed for the web server to talk to the AS server.



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!