Linked table password exposure in Access 2003

M

MarkInSalemOR

In Access 2000 the password is exposed in the MSysObjects table as part of
the DSN. As a result my work is requiring me to go to a lot of extra
programming work so I don't have to link the tables. Does Access 2003 correct
this problem or is the password still visible like it's been in Access 2000?

It's ironic they won't give me VB6 but in the end it's VB6 that I'm doing in
the Access environment. Most of the Access power features are essentially
useless to me without the linked tables.

And am I missing an undocumented option, VBA workaround, etc, that would
allow me to encrypt or hide it in 2000? And whatever method is used makes the
information secure even if someone links in the table.

Thanks
Mark
 
M

MarkInSalemOR

I've done more research and at least Microsoft isn't the only company with
old methods of password storage in plain English. If I choose to store my
password when creating the ODBC connection for DB2 (using DB2 software to
make this connection) it stores the password in plain English in an .ini file.

So another question, is there an event that's fired when someone links into
an mdb? Said another way, is there a way I can write code in an mdb that will
prevent someone from linking in or will kill the linked tables when someone
tries to link in.

Darn good thing the firewall admins do a reasonably good job of keeping
people out. It's a major pain to keep these things secure in case a hacker
makes it by the firewall.

Mark
 
D

Douglas J. Steele

I suppose one way would be to store the password encrypted somewhere, then
recreate the links everytime you open the application, decrypting the
password to do so. When closing the application, either delete the links, or
set them to something with an incorrect password.
 
Top