J
JohnE
Hello. I have a situation in which I am working on an A2003 app (front end)
that is connected to a SQL 2005 backend. This app is also being looked at
going over to A2007, but still remain (if possible) a mdb file.
What I am running into is the notice that keeps asking for the sql ID and
password. The database application is linked to data tables that actually
reside on a different server, for example on one of our SQL servers. Once the
initial message box is closed, the reason the login failed is then displayed.
This is the dialog box that has the checkbox for trusted connection, ID,
Password, etc. Access is trying to log in to the SQL server using the name
used to log in to the computer (windows authentication). Most of our SQL
Server databases require their own login names and passwords. The checkbox
next to "Use Trusted Connection" is cleared and then you can enter the
correct name and password in the corresponding boxes.
This is not how this inherited db app has worked. In A2003, everything
worked just fine on the connections, etc.
The A2003 app has been around for 10+ years. It was A97 before A2003. Now
A2007 is being moved out to the company in Q4 and this app needs to be ready
to run on it.
Has anyone also had this dilemma and if so how did you resolve it? I am at
a loss here and have no idea how to proceed.
Thanks.
.... John
that is connected to a SQL 2005 backend. This app is also being looked at
going over to A2007, but still remain (if possible) a mdb file.
What I am running into is the notice that keeps asking for the sql ID and
password. The database application is linked to data tables that actually
reside on a different server, for example on one of our SQL servers. Once the
initial message box is closed, the reason the login failed is then displayed.
This is the dialog box that has the checkbox for trusted connection, ID,
Password, etc. Access is trying to log in to the SQL server using the name
used to log in to the computer (windows authentication). Most of our SQL
Server databases require their own login names and passwords. The checkbox
next to "Use Trusted Connection" is cleared and then you can enter the
correct name and password in the corresponding boxes.
This is not how this inherited db app has worked. In A2003, everything
worked just fine on the connections, etc.
The A2003 app has been around for 10+ years. It was A97 before A2003. Now
A2007 is being moved out to the company in Q4 and this app needs to be ready
to run on it.
Has anyone also had this dilemma and if so how did you resolve it? I am at
a loss here and have no idea how to proceed.
Thanks.
.... John