Re: MS Access linked tables SQL Server

From: Mary Chipman [MSFT] (mchip_at_online.microsoft.com)
Date: 09/22/05

  • Next message: Christopher Pankhurst: "Strange requirement for linked server" 
    Date: Thu, 22 Sep 2005 13:20:07 -0700

    What do you mean by "secure"? When that term is used in conjuction
    with Access, the word "oxymoron" usually follows :-) First of all, the
    DSNs are not secure, and if you are saving the linked tables between
    sessions, neither are they because Access caches schema and connection
    information locally. The recommend course of action is to write code
    that links the tables dynamically for each session, passing the
    connection string information directly, not using DSN's. then delete
    the tabledef objects when the app shuts down (and also when it starts
    up prior to relinking). Even when you do that, the data is still not
    encrypted, but at least it's a start.

    --Mary

    On Tue, 20 Sep 2005 15:00:28 -0700, "John" <IDontLikeSpam@Nowhere.com>
    wrote:

    >Hello,
    >
    >We have a bunch of client machines that use MS Access (pretty sure all of
    >them are XP) that has linked tables to our SQL Server 2000 database which is
    >on it's own domain and server. I was wondering if the data that is
    >traveling between each client that connects to our SQL Server (linked tables
    >from MS Access using the ODBC dsn in the control panel) is encrypted and/or
    >secure? I think I read somewhere on the internet that MDAC 2.6 or higher
    >the encryption is used by default? Just hoping someone could confirm to me
    >that this is true. Thanks in advance.
    >
    >John
    >

  • Next message: Christopher Pankhurst: "Strange requirement for linked server"

    Relevant Pages