T
Tony
Hi all!
I am having a rather odd issue with VB.Net (Visual Studio 2005) and SQL
Server 2005. I developed a little app for our team but then decided to
make it available for others. Since out team was given admin rights to
our database, I used integrated security for the first version of the
app. When I opened it up to other groups, I changed to SQL
authentication.
The problem is that no one outside our group has been able to use the
app because of DB connection issues. It always works from my machine,
so I checked the activity monitor on the server. Sure enough, I am
logged in as myself instead of the user I set up for the application.
Here is the connection string:
Private m_SQLConStr As String = "Data Source=MYDB;Initial
Catalog=MYDATA;Integrated Security=False;Persist Security
Info=False;User ID=MYUSER;Password=MYPASSWORD"
Does anyone have any insight into this problem?
Thanks!
I am having a rather odd issue with VB.Net (Visual Studio 2005) and SQL
Server 2005. I developed a little app for our team but then decided to
make it available for others. Since out team was given admin rights to
our database, I used integrated security for the first version of the
app. When I opened it up to other groups, I changed to SQL
authentication.
The problem is that no one outside our group has been able to use the
app because of DB connection issues. It always works from my machine,
so I checked the activity monitor on the server. Sure enough, I am
logged in as myself instead of the user I set up for the application.
Here is the connection string:
Private m_SQLConStr As String = "Data Source=MYDB;Initial
Catalog=MYDATA;Integrated Security=False;Persist Security
Info=False;User ID=MYUSER;Password=MYPASSWORD"
Does anyone have any insight into this problem?
Thanks!