Ok, so the moral of this story, use a domain account to run your asp.net process when you need to access network resources on the same domain. Well, that's the moral I used anyway. If anybody has other solutions to this, I'd like to hear them too. Here's an article for asp.net 1.1 which I took bits and pieces of to get the solution working http://msdn2.microsoft.com/en-us/library/aa302396.aspx[^] Keith

Each time a page is requested from the server your session timeout is reset. If you are not worried about a million users using the page, and leaving it open try this. Make a 0 sized frame, and make some timer refresh that page every 19 minutes. The only way to speed up a Macintosh computer is at 9.8 m/sec/sec.

Just to cap this off, whatever the problem was became fixed after doing a iisreset. I discovered this on accident while attempting to get remote debugging running. So one problem down, one to go.

Very interesting. Well, that throws the conventional wisdom out of the window.:-D the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer Deja View - the feeling that you've seen this post before.

I totally agree about the maintenance issue that arises from having so many subclassed tables in such a query. I began to explore a different path and ended up not going with huge query that you suggested. I'm trying my "bestest" to do an n-tier approach and that huge query didn't fit right with what I had. Though who knows if I'm doing it close to right. lol Thanks again. Keith

Ahh yes...it's all about the vocab. *sigh* I'll do some more searching. In fact, I already found some good things...hopefully. Thanks.

Scott Serl wrote: On projects that require closer auditing, I use triggers to log changes to another database. That way, even admins changes through queries are logged. Excellent point :-D