Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Linked table password exposure in Access 2003

Discussion in 'Information Technology' started by MarkInSalemOR, Nov 19, 2005.

  1. MarkInSalemOR

    MarkInSalemOR
    Expand Collapse
    Guest

    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
     
  2. Loading...

    Similar Threads Forum Date
    Opinion Letter: When terrorism is falsely linked by race or religion, we all become the victims Breaking News Apr 27, 2013
    SciTech Law of Entropy Linked to Evolution of Intelligence Breaking News Apr 23, 2013
    Canada GM corn linked to early death in new study Breaking News Sep 22, 2012
    India set to ban 100 Al Qaeda-linked groups Hard Talk May 17, 2010
    Sikh News Temple linked to terrorists still active (Moldova.org) Breaking News Feb 5, 2008

  3. MarkInSalemOR

    MarkInSalemOR
    Expand Collapse
    Guest

    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

    "MarkInSalemOR" wrote:

    > 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
     
  4. Douglas J. Steele

    Douglas J. Steele
    Expand Collapse
    Guest

    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.

    --
    Doug Steele, Microsoft Access MVP
    http://I.Am/DougSteele
    (no e-mails, please!)



    "MarkInSalemOR" <MarkInSalemOR@discussions.microsoft.com> wrote in message
    news:7E43BFD1-ECA1-403D-AF2C-C6D052873C8C@microsoft.com...
    > 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
    >
    > "MarkInSalemOR" wrote:
    >
    >> 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
     

Share This Page