MS Access 2000 and MS SQL 2000

[Guest]

I have a user application that runs on MS Access 2000. On one client PC, the
user's PC log in and got the following error:
17[Microsoft][ODBC SQL Server Driver][DBNETLIB]AQL Server does not
exist or access denied.:53[Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionOpen(Connect())..

Its very strange because when I log into the same PC with local admin
rights, or with my ID, I have no problem to login to system. However, when
the user try her login, the above error occurs.

Initial diagnose thought it was MDAC, but I doubt. Any one has any idea
what is the cause?

Thanks in advance.

 

[Guest]

Hi Sam,

Sounds like a permissions problem - does the user have rights to the SQL
Server that may be necessary?

You could also check that the ODBC connection is working by opening Data
Sources (ODBC) under Control Panel-->Administrative Tools and testing the
connection.

Damian.

 

[Van T. Dinh]

If you use Windows Pass-through Authentication on the SQL Server, does the
user have permission to access the required database on the server?

If you use SQL Server Authentication and you store the SQL login/ password
in the ODBC DSN then check the DSN.

 

[Guest]

I use SQL Login.
When I test the connection in ODBC, it works!
But when I am at Access 2000, and try to attach tables, it hang there for
some time and then the message appears!
How do i check for DSN by the way?

Please help!
Thanks.

If you use Windows Pass-through Authentication on the SQL Server, does the
user have permission to access the required database on the server?

If you use SQL Server Authentication and you store the SQL login/ password
in the ODBC DSN then check the DSN.

--
HTH
Van T. Dinh
MVP (Access)

I have a user application that runs on MS Access 2000. On one client PC,
the
user's PC log in and got the following error:
17[Microsoft][ODBC SQL Server Driver][DBNETLIB]AQL Server does not
exist or access denied.:53[Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionOpen(Connect())..

Its very strange because when I log into the same PC with local admin
rights, or with my ID, I have no problem to login to system. However,
when
the user try her login, the above error occurs.

Initial diagnose thought it was MDAC, but I doubt. Any one has any idea
what is the cause?

Thanks in advance.

 

[Van T. Dinh]

I assume you tried with the user's Windows login (which would pick up the
ODBC DSN that uses by the user)?

DSN is Data Source Name, basically those entries you find in the Data
Sources (ODBC) under Administrative Tools of the OS. Log in to the PC as
the user, find the entry in the User DSN and check login / password plus the
network library under the "Client Configuration ... " button. Test and make
sure that the connection works.

If the above OK, check the database again. You might also like to try just
setting up 1 or 2 linked Table in a new test / blank database file. If you
can't it is like that the user has access to the database but no access
permission to the Tables.

 

[dbahooker]

you're a ****ing idiot.. if you're using MDB against SQL Server


Access Data Projects make it a LOT easier to deal with.. you don't need
to set strings for each object; just ONCE under FILE/CONNECTION

don't listen to these MDB wannabes-- they should be SPIT ON

-Aaron

 

[susiedba]

I agree with DbaHooker... but im not going to be sooo rude about it

Hope that helps

ps - if you're using Access Data Projects; make sure you've got the
latest patches installed; specifically for Access 2000-- it needs a
patch for sure

-Susie