You probably saw my reply to Rick.

I'm still not sure what's going on, but I'm not going to worry about it too much at this point ... I've got too much other stuff going on and it's not really an issue for any of our customers right now, especially since I've figured out that adding the login to SQL Server solves the problem ... and, from what everyone has been saying, that's the way it should have been all along anyway <g> ... which I probably knew at one time but have forgotten. <g>

We've not deployed a 2.0 app yet anyway ... we're in the process of upgrading our existing 1.1 app.

Thanks for your help!! =)

~~Bonnie




>Yes add login and adjust what databases, what it can "select" etc.
>I don't know. Maybe you used "windows" for your login security check.
>Cetin
>
>>Ok, Cetin .... and how did you grant the rights to the ASPNET account? Add a login to SQL Server with Enterprise Manager? I DID NOT HAVE a login to SQL Server for ASPNET prior to running into this problem with 2.0. I am 100% sure of that. I am also pretty sure that I didn't use impersonation (there's nothing in the web.config).
>>
>>Maybe something in the machine.config? I'll have to look into that, because I can't remember what kind of stuff gets put into the machine.config (it's been so long since I had to do any configuration stuff <g>).
>>
>>~~Bonnie