Gustav Brock
gustav at cactus.dk
Thu Oct 21 11:37:45 CDT 2004
Hi Gary Couldn't you try to open a connection to the database? Pick the connect string from one of the tables and add a leading "ODBC;": strConnect = "ODBC;" & tdf.Connect Set wrk = DAO.CreateWorkspace("wrkVerify", vbNullString, vbNullString, dbUseODBC) ' Open ODBC connection for read/write using the connection string. Set cnn = wrk.OpenConnection("cnnVerify", dbDriverNoPrompt, False, strConnect) ' If this fails, username and/or password may be wrong. ' Prompt for these. Set cnn = wrk.OpenConnection("cnnVerify", dbDriverPrompt, False, strConnect) ' If this succeeds, save the connect string and use it to relink ' the tables. ' Update connection information. strConnect = cnn.Connect This is DAO. You could probably do something similar with ADO. You will, of course, need to add code to catch and handle errors. /gustav > I have been using the Microsoft ODBC for Oracle Driver version 2 build > 2.573.6200.00 for a few years to access Oracle 8 and 9 databases on a > read only basis. All was well until the Oracle DBA's decided - or were > forced to due to Sarbaine/Oxley legislation - make the passwords > expire on a periodic basis on the Oracle user account that is used for > the ODBC connection. The ODBC driver I am currently using doesn't seem > to have the ability to allow the password to be changed, it just fires > an error message window when the expired password is encountered. > ODBC-call failed. Error ORA-28001: the password has expired > The users could access the acount through SQL+ or another Oracle > terminal tool like SQL Navigator or TOAD but that would be considered > another security risk, so they don't want to provide any of those > tools to the users. They want the users themselves to be able to > change the passwords so that only they will know what the password is > for their account. > Anybody run into this or have any ideas? > -- > Gary Kjos > garykjos at gmail.com