You could use the old iframe trick. You can load an iframe with anything the client has access to, have the iframe hidden, and access its contents via javascript. What we use to do before XMLHTTPRequest was ubiquitous but more work involved.

Let me know when you work this out. :rolleyes: only two letters away from being an asset

You can't convert a HttpRequest object to a WebRequest object, so you have to copy the information you want from one object to the other. --- single minded; short sighted; long gone;

You could set up a sub-domain that is password protected and has its own database. Something like test.domain-name.com as a sub-domain of www.domain-name.com. I do that for development and testing of new features to a production site so that only authorized people can gain access and the new features can be throughly tested on the actual web server that they will eventually be deployed on. That model would also work for rolling out new web services. You could throughly test the services before cut over to the production domain. Simply Elegant Designs JimmyRopes Designs Think inside the box! ProActive Secure Systems I'm on-line therefore I am. JimmyRopes