neil_turner
Registered User.
- Local time
- Today, 18:02
- Joined
- Mar 4, 2002
- Messages
- 16
Hi All..
Quick question.. I'm creating a project where all the major database tables are on Oracle with only a few application tables within Access (although they don't really need to be - they can be located in Oracle should I need to). At present so that I can update some of the oracle tables I need to perform at least a 2 table join and hence I'm using ODBCdirect. I'm also using MS Jet to fire information into bound forms (just for ease really).
What I'd like to know, is there anyway that the username and password for a linked table can be obtained as such to create an connect string. I understand that this would probably open up some sort of hole in the security of the application. What I'm trying to achieve is the need to only change the DSN, username and password once (as the application will be pointed at different database's as it gets deployed) Instead of storing encrypted details for the ODBCdirect connection, and then changing the connection details for the linked tables!
Alternatively is there any error that can be trapped for a linked table should the connection details not be supplied?
Many Thanks
Neil
Quick question.. I'm creating a project where all the major database tables are on Oracle with only a few application tables within Access (although they don't really need to be - they can be located in Oracle should I need to). At present so that I can update some of the oracle tables I need to perform at least a 2 table join and hence I'm using ODBCdirect. I'm also using MS Jet to fire information into bound forms (just for ease really).
What I'd like to know, is there anyway that the username and password for a linked table can be obtained as such to create an connect string. I understand that this would probably open up some sort of hole in the security of the application. What I'm trying to achieve is the need to only change the DSN, username and password once (as the application will be pointed at different database's as it gets deployed) Instead of storing encrypted details for the ODBCdirect connection, and then changing the connection details for the linked tables!
Alternatively is there any error that can be trapped for a linked table should the connection details not be supplied?
Many Thanks
Neil
