Re: authentication

Check the permissions levels and make sure that each person is running
their own copy from their own workstation. Access front-ends should never be
shared.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
"JohnE" <JohnE@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9BD92337-9C4C-456F-B215-73BD6427A902@xxxxxxxxxxxxxxxx
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



.

Relevant Pages

  • Re: Problems connecting to SQL-Server
    ... Where do i "click" to grant access with a login in SQL Servers? ... >>Our app uses ADO.NET and the database is MS SQL Server. ...
    (microsoft.public.sqlserver.connect)
  • authentication
    ... I have a situation in which I am working on an A2003 app ... that is connected to a SQL 2005 backend. ... for example on one of our SQL servers. ... This is the dialog box that has the checkbox for trusted connection, ID, ...
    (microsoft.public.access.formscoding)
  • Re: authentication
    ... The permissions are fine within Access as well as SQL ... Everyone using the app is still using the ... reside on a different server, for example on one of our SQL servers. ... This is the dialog box that has the checkbox for trusted connection, ID, ...
    (microsoft.public.access.formscoding)
  • Re: authentication
    ... Everyone using the app is still using ... What I am running into is the notice that keeps asking for the sql ID ... reside on a different server, for example on one of our SQL servers. ... This is the dialog box that has the checkbox for trusted connection, ...
    (microsoft.public.access.formscoding)
  • Re: Access vs SQL
    ... from Access, tweaked my app a bit, and viola, everything works. ... MSDE 2000 adds a bit of complexity, but I have to say, compared to ... > (above and beyond what they pay for my engineering services). ... > Now, still using C1 components, I know I can upsize to MSDE or SQL ...
    (microsoft.public.dotnet.languages.vb)
Quantcast