Here is an update to my problem I posted above.īy creating a new Access database file I determined that I could successfully link a table with the Oracle driver. But, I'm wondering if the way Oracle manages the tables causes the problems.ĭoes anyone have anything else they can add or have me try? One extra point I can add is that I have tried to link to both public synonyms and actual tables in Oracle. Since I have the same problem I was hoping someone else on other sites may have an answer.

Overall, the problem on the other site was never solved. I have tried the following drivers for Oracle: Microsoft's driver, Oracle's 9.2 driver, and Oracles 10.2.0.3 driver. So, that is why I asked here for a way to solve the problem just from the perspective of opening the table in data view.Ĥ. If simply opening the table in data view doesn't work, then nothing else would work (is what I am assuming). Dynamically building the ODBC connection string is what I do in the application.

The 'Save Password' checkbox should not be selected when linking a table because that means anyone that gains access to the. It is best to keep connection information stored in a separate file (as I am using a FILE DSN).Ģ. mdb file needs to be modified every time it is deployed to a new environment. DSN-Less connections are not a good idea because this means the. The other options do not work as follows:ġ. I have tried the same options, but it is only when the ODBC driver is switched to Oracle that the password prompt appears. But, the other options on the site you mention do not solve the problem. I did post this question on three different sites. What is going on here? Why is Oracle's 10.2.0.3 ODBC driver not storing the I cannot solve this by checking the 'Save Password' box while initially linking the tables (won't work with my requirements). Furthermore, IĪm prompted for the password two times (the prompt window comes up once, IĪdd the password, and then it appears again and I add the passwordĪgain-then the data view is displayed).

The table is opened-even if I have previously supplied it. When I now have removed the tables and linked them again to an Oracleĭatabase using Oracle's ODBC driver, the password prompt comes up EVERY time To that same Sybase database are not prompted for the username and password. In data view, it prompts me for the username and password. Linked to a Sybase database using Sybase's ODBC driver. I am in a conversion of the application to move it from linking from Sybase Linked tables are created without checking the 'Save Password' box in each instance Time a table was opened (which was good). When Sybase was used, the password prompt only was shown the first Is that with the Oracle driver the password prompt appears every single time the table I have a problem converting linked tables in MS Access from Sybase to Oracle.

Ms access password storage