John,

Accessing SQL through a Web Service is different. Apparently ASP.NET needs to have certain rights to the SQL Server. I'm just having a hard time finding how to set these, especially since I'm 95% sure this worked in VS2003 and I don't remember doing anything special (but I haven't had a chance to verify that, *and* I could be remembering it wrong ... the memory is slowly going as I get to be an old fart <g>).

[UPDATE] -- I did manage to test this out in ASP.NET 1.1, and my memory hasn't failed me yet <g> ... it works fine with a Trusted_Connection through a 1.1 WebService.

~~Bonnie


>Hi:
>
>At work we use truested connections (I'm assuming you mean windows authentication) all the time, but the windows user name has to be a user of the sql database in question. Once we did that, we have no trouble logging in via a connection string using trusted connections.
>
>
>
>>I'm sure this is a known problem, but I can't seem to find the fix.
>>
>>My VS2005 app connects to the SQL Server database through web services. If I connect with a connection string that uses userid and password, no problem. But, if I change that to use a Trusted_Connection instead, it won't work.
>>
>>This worked fine when the app was compiled under VS2003, but has not since migrating it to VS2005. Is there some setting I need to tweak somewhere? In IIS maybe? This is only a problem with Web Services.
>>
>>TIA,
>>
>>~~Bonnie