-
1
- #1
Afternoon everyone!
Am not quite sure if this is the correct forum to post this topic, so here goes...
I would really be grateful for some advice regarding the above matter (note: am novice to the 'client/server' implementation, so would ask for your patience, pls!):
We have a front-end Access 2K app’n, which connects to some back-end data, (using a 'dsn-less' ODBC link (Access table)). The system was not in use for several months, during which time the server was re-built.
The problem I’m having is that although I can connect to the back-end data, the other users are unable to do this.
I have been looking into the problems/issues encountered so far, including:
· - Updating the dsn-less connection table within the front-end Access application (note: we have other applications which use this method for connectivity, without any problems here), i.e.
ODBC;Driver={SQL Server};APP=Microsoft Access;UID={updated username};PWD={updated password};Server={name of server};DATABASE={name of database on server}
· Re-visiting the ‘ODBC Data Source Administrator’ and checking the configuration of the ‘Microsoft SQL Server DSN Configuration’ (i.e. ‘Window authentication, using the network login’, etc).
The strange thing is that I’m able to access the back-end data, via the application without any problems at all (I’m using the full version of MS Access 2K, as need to eventually make changes to the front-en app’n. All of the users have MS Access 2K run-time only installed).
However when the user tries to log, they acquire ‘ODBC—connection to {Access application name} failed’ messages.
Up to three other users have tried to access the system, and acquire error message of the following nature:
Within the front-end application:
· ‘The {Access application name} is not available (Error No: 3151. Error: ODBC—connection to {Access application name}’ failed.)
· (1) Initially the user obtains the message: ‘The expression you entered has a function that ‘{Access application name}’can’t find.’ Then (2) I receive an ‘Action Failed’ on the ‘AutoExec’ macro (this is set up to execute a function which acquires the user’s window’s login details).
Linking to the back-end data:
· Connection failed: SQLState: ‘28000’. SQL Server Error: 18456. [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ‘{domain_name}\{users_Windows_login_name}’.
· Whilst user was logged in at my desktop, I tried to implement a ‘SQL Server ODBC Data Source Test’. However the ‘Test Results’ have been as follows
“Microsoft SLQ Server QDBC Driver Version 03.85.1117. Running connectivity tests… Attempting connection [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ‘{domain_name}\{users_Windows_login_name}’.
We currently have other client/server applications which link using the above methods (ODBC dns-less connections, etc), but have no problems with the user’s and their permissions to access these.
Would appreciate any help/suggestions/advice, etc with this.
Many thanks in advance.
Magnetar
![[atom]](/data/assets/smilies/atom.gif "[atom] [atom]")
Am not quite sure if this is the correct forum to post this topic, so here goes...
I would really be grateful for some advice regarding the above matter (note: am novice to the 'client/server' implementation, so would ask for your patience, pls!):
We have a front-end Access 2K app’n, which connects to some back-end data, (using a 'dsn-less' ODBC link (Access table)). The system was not in use for several months, during which time the server was re-built.
The problem I’m having is that although I can connect to the back-end data, the other users are unable to do this.
I have been looking into the problems/issues encountered so far, including:
· - Updating the dsn-less connection table within the front-end Access application (note: we have other applications which use this method for connectivity, without any problems here), i.e.
ODBC;Driver={SQL Server};APP=Microsoft Access;UID={updated username};PWD={updated password};Server={name of server};DATABASE={name of database on server}
· Re-visiting the ‘ODBC Data Source Administrator’ and checking the configuration of the ‘Microsoft SQL Server DSN Configuration’ (i.e. ‘Window authentication, using the network login’, etc).
The strange thing is that I’m able to access the back-end data, via the application without any problems at all (I’m using the full version of MS Access 2K, as need to eventually make changes to the front-en app’n. All of the users have MS Access 2K run-time only installed).
However when the user tries to log, they acquire ‘ODBC—connection to {Access application name} failed’ messages.
Up to three other users have tried to access the system, and acquire error message of the following nature:
Within the front-end application:
· ‘The {Access application name} is not available (Error No: 3151. Error: ODBC—connection to {Access application name}’ failed.)
· (1) Initially the user obtains the message: ‘The expression you entered has a function that ‘{Access application name}’can’t find.’ Then (2) I receive an ‘Action Failed’ on the ‘AutoExec’ macro (this is set up to execute a function which acquires the user’s window’s login details).
Linking to the back-end data:
· Connection failed: SQLState: ‘28000’. SQL Server Error: 18456. [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ‘{domain_name}\{users_Windows_login_name}’.
· Whilst user was logged in at my desktop, I tried to implement a ‘SQL Server ODBC Data Source Test’. However the ‘Test Results’ have been as follows
“Microsoft SLQ Server QDBC Driver Version 03.85.1117. Running connectivity tests… Attempting connection [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ‘{domain_name}\{users_Windows_login_name}’.
We currently have other client/server applications which link using the above methods (ODBC dns-less connections, etc), but have no problems with the user’s and their permissions to access these.
Would appreciate any help/suggestions/advice, etc with this.
Many thanks in advance.
Magnetar