Hi, Bill-

>One possibility to throw into the pool for thought is to not run under the ASPNET worker account, but use impersonation to run under an account that has rights to the necessary resources. I have an application here I am doing that with in an Intranet scenario. There are security issues, of course, with higher privileged accounts but just a thought to generate more thought on the issue.

Thanks for your help. Impersonation did indeed turn out to do the trick.