We are using Oracle databases for inventory control and connecting to them for reporting with several Access 97 databases running on Windows XP pro workstations. Recently we changed the Oracle password, removing the write access permissions for these small DB's. We relinked every table in every database using the new password and everything works- almost.
The first time a user tries to access a database after the computer is started he/she gets a ODBC failure message. At that point the user needs to link or relink a table (at random- the table itself does not need to be used) or even manually open one of the linked tables and suddenly all the links to that database are active. Since the Access 97 front ends link to 5 separate databases, this becomes a nuisance.
I have re-linked to the Oracle databases (many times), deleted the ODBC sources and re-built them, rebuilt the Oracle alias’ using SQL EasyNet configuration, Checked the TNSNAMES.ORA file, renamed it and recreated it , again using EasyNet. .
Has anyone heard of this particular problem and does anyone have any suggestions?
Thanks
Bruce
The first time a user tries to access a database after the computer is started he/she gets a ODBC failure message. At that point the user needs to link or relink a table (at random- the table itself does not need to be used) or even manually open one of the linked tables and suddenly all the links to that database are active. Since the Access 97 front ends link to 5 separate databases, this becomes a nuisance.
I have re-linked to the Oracle databases (many times), deleted the ODBC sources and re-built them, rebuilt the Oracle alias’ using SQL EasyNet configuration, Checked the TNSNAMES.ORA file, renamed it and recreated it , again using EasyNet. .
Has anyone heard of this particular problem and does anyone have any suggestions?
Thanks
Bruce
