>>Hi,
>>
>>When calling a stored procedure from a simple/test .NET project and using "sa" for user ID I get error
>>
>>Login failed for user 'sa'
>>The user is not associated with a trusted SQL connection
>>
>>
>>In comparison, when calling SQL from my VFP application I have connection string with [Trusted_Connection=Yes]. Is this what is missing in my .NET connection string? If so, who do I specify it in my .NET connection string?
>>
>>TIA
>
>Dmitry,
>
>IMHO, you should not even try to use sa account to access data from your application. You need to have a separate login and give it minimum rights. May be the error you're getting is a precaution from trying to access database by sa password from the application.
I don't think I have a password 'sa' set in my database. But I need - somehow - to have access to the database right now from .NET method. And I have no password to use. In VFP connection string I don't specify a password and I thought that the same could be applied to .NET world. When I use MSSMS to access my SQL DB I have Windows Authentication.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
