"Brad" <ballison@ukcdogs.com> wrote in message
news:euVujA8qEHA.1036@TK2MSFTNGP10.phx.gbl...
> Found the problem!
>
>
> "Brad" <ballison@ukcdogs.com> wrote in message
> news:ezOBFp6qEHA.2856@TK2MSFTNGP10.phx.gbl...
>> Okay, I know this subject has probably been beat to death, but here is my
>> situation:
>>
>> I have an instance of MSDE over a network. I created a VB program that
>> uses the MSDE instance as the data store. On installing the program on a
>> couple of PCs the program works just fine and I do not get any errors.
>> On the remaining PCs I am getting the dreaded "Not associated witha
>> trusted SQL Server connection <null> user".
>>
>> Now in a matter of deduction, I don't think it is the connection string
>> used in the program because this is working on the first four PCs I
>> installed the program to. Every PC shares the same domain, by the way.
>> We are a small company with under 100 PCs. But why would this come up on
>> only a couple of PCs?
>>
>> I have set these users up on the actual PC that has MSDE and assigned
>> Administrative rights to these users. Thinking this would grant them
>> access to the data store. Still have the same problem.
>>
>> Thanks for any insight into what else I might try or what I am doing
>> wrong.
>>
>> Brad
>>
>
>

"Brad" <ballison@ukcdogs.com> wrote in message
news:ezOBFp6qEHA.2856@TK2MSFTNGP10.phx.gbl...
> Okay, I know this subject has probably been beat to death, but here is my
> situation:
>
> I have an instance of MSDE over a network. I created a VB program that
> uses the MSDE instance as the data store. On installing the program on a
> couple of PCs the program works just fine and I do not get any errors. On
> the remaining PCs I am getting the dreaded "Not associated witha trusted
> SQL Server connection <null> user".
>
> Now in a matter of deduction, I don't think it is the connection string
> used in the program because this is working on the first four PCs I
> installed the program to. Every PC shares the same domain, by the way.
> We are a small company with under 100 PCs. But why would this come up on
> only a couple of PCs?
>
> I have set these users up on the actual PC that has MSDE and assigned
> Administrative rights to these users. Thinking this would grant them
> access to the data store. Still have the same problem.
>
> Thanks for any insight into what else I might try or what I am doing
> wrong.
>
> Brad
>

"William (Bill) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message
news:OuAqEV8qEHA.556@tk2msftngp13.phx.gbl...
> So, would you care to share it with the group?
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
>
> "Brad" <ballison@ukcdogs.com> wrote in message
> news:euVujA8qEHA.1036@TK2MSFTNGP10.phx.gbl...
>> Found the problem!
>>
>>
>> "Brad" <ballison@ukcdogs.com> wrote in message
>> news:ezOBFp6qEHA.2856@TK2MSFTNGP10.phx.gbl...
>>> Okay, I know this subject has probably been beat to death, but here is
>>> my situation:
>>>
>>> I have an instance of MSDE over a network. I created a VB program that
>>> uses the MSDE instance as the data store. On installing the program on
>>> a couple of PCs the program works just fine and I do not get any errors.
>>> On the remaining PCs I am getting the dreaded "Not associated witha
>>> trusted SQL Server connection <null> user".
>>>
>>> Now in a matter of deduction, I don't think it is the connection string
>>> used in the program because this is working on the first four PCs I
>>> installed the program to. Every PC shares the same domain, by the way.
>>> We are a small company with under 100 PCs. But why would this come up
>>> on only a couple of PCs?
>>>
>>> I have set these users up on the actual PC that has MSDE and assigned
>>> Administrative rights to these users. Thinking this would grant them
>>> access to the data store. Still have the same problem.
>>>
>>> Thanks for any insight into what else I might try or what I am doing
>>> wrong.
>>>
>>> Brad
>>>
>>
>>
>
>