P
PSULionRP
Interesting anomaly.
We have one business user that is receiving this error message when
attempting to open and execute a Microsoft Access Database Application. Just
one out of like 6 or 7.
The application prompts for her User ID and Password. Her ODBC has been
set-up with the same parameters that everyone else has. I had her check for
her TNSNAMES.DSN file and it is out there and is up-to-date as to being
pushed to her client machine.
Here are some specifics regarding the Microsoft Access Database.
- It uses ADO to access its data. The ODBC check simply SELECTS a MIN from a
Pass-Through Query to ensure connectivity
- We are accessing an Oracle 10g Database
- The ODBC was set-up utilizing the Oracle9iclient driver
- The Microsoft Access Database is Access 2003
Can anyone shed any light on this for me???
Thanks for reviewing and hopeful for a reply.
PSULionRP
We have one business user that is receiving this error message when
attempting to open and execute a Microsoft Access Database Application. Just
one out of like 6 or 7.
The application prompts for her User ID and Password. Her ODBC has been
set-up with the same parameters that everyone else has. I had her check for
her TNSNAMES.DSN file and it is out there and is up-to-date as to being
pushed to her client machine.
Here are some specifics regarding the Microsoft Access Database.
- It uses ADO to access its data. The ODBC check simply SELECTS a MIN from a
Pass-Through Query to ensure connectivity
- We are accessing an Oracle 10g Database
- The ODBC was set-up utilizing the Oracle9iclient driver
- The Microsoft Access Database is Access 2003
Can anyone shed any light on this for me???
Thanks for reviewing and hopeful for a reply.
PSULionRP