Well I had to put client tools on the server that held the MSDE. Only then could I ADD the user machinename\ASPNET as a user into the database.

Tool lots of attempts before i just added the client tools. Lesson learned was "It's a rights thing".

Thanks for your help

__Stephen

>Try logging into your desktop as ASPNET. Then try to access the database. This will test to make sure the domain user is setup properly.
>
>>MSDE is set up for Windows Authentication, 99.9% sure but there is an admin with a quick reaction to fix things here. A quick check from my desktop EM and yes it's set for WA.
>>
>>I can do anything with the database from EM, QA, or even my .NET IDE Server Explorer. It's just when I change the sever name in :
>>string strConnection = "SERVER=STEPHEN-LAPTOP;Trusted_Connection=Yes ";
>>to
>>string strConnection = "SERVER=CHDIIS;Trusted_Connection=Yes ";
>>it fails with the error that is this subject.
>>
>>__Stephen
>>
>>
>>>Can you access the database from the designer? Is MSDE setup for Windows authentication or Mixed?
>>>
>>>>Cathi, I have done those and no go. Seems that I am getting a machinename\ASPNET comming in as the user.
>>>>
>>>>Does this ring a bell for a fix?
>>>>
>>>>>Stephen,
>>>>>
>>>>>Make sure ASPNET has been added to MSDE as a user with sufficient rights.
>>>>>
>>>>>>I have a trusted connection SQL Server security inplace on both my laptop and the MSDE that I put up on a clients test server. When I run from my laptop things are good. When I try to use the identical data from his server I get an error:
>>>>>>
>>>>>>Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
>>>>>>
>>>>>>I am part of the domain and I have rights. I had an admin create an account for ASPNET, and I placed it in the server list of users. Gave it dbo rights and still no go.
>>>>>>
>>>>>>Any ideas on this security thing?
>>>>>>
>>>>>>TIA
>>>>>>
>>>>>>__Stephen