>You may have to set up impersonation for you app.
>

I thought of that, Bob, but it seems to be a bit of a kludge, doesn't it? I mean, if the default behavior is to run under the NETWORK SERVICE account, and that account shares all the limited permissions and benefits of the ASPNET account (which the documentation claims), and the NETWORK SERVICE account (apparently) already exists, doesn't that suggest that you simply grant access to the database for that account?

If that is indeed the only way to make this work, are you thinking that I should impersonate the ASPNET account?

It could be that this is some kind of weird security "feature", though at this point I can't see the benefit <s>. All I can think of is that because it would take some serious hacking to modify the web.config file, and you have no choice - you *must* use impersonation to get at the SQL Server data, because the NETWORK SERVICE account is some kind of weird "hidden" account...does this make things more secure?

I dunno

>>-Steve->>

Steve Sawyer
Geeks and Gurus, Inc.