Re: MS Access linked tables SQL Server

From: Noone (IDontLikeSpam_at_nowhere.com)
Date: 09/23/05

  • Next message: Jaime Sepulveda: "SQL 2000 Audit"
    Date: Fri, 23 Sep 2005 08:02:55 -0700
    
    

    Thanks for your post Mary. I think I understand the picture a little better
    now since I read some articles about installing a certificate onto our SQL
    Server which then I use the Server Network Utility and enabled the Force
    Protocol Encryption selection so that all connections to the SQL Server are
    encrypted. Now all ODBC connections need to have at least the MDAC 2.6 or
    higher which clears things up for me :0)

    "Mary Chipman [MSFT]" <mchip@online.microsoft.com> wrote in message
    news:h346j15h5l0u3b8qvpa416tavms4dlt4va@4ax.com...
    > 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: Jaime Sepulveda: "SQL 2000 Audit"

    Relevant Pages

    • Re: Dot Net 2.0 or SQL Server 2005 problem?
      ... Assume the SQLExpress set up is OK, whther you can actually access the SQL ... After installing SQL Server Express, if you did not add any SQL login ... Configuration' and set the option to 'Using Both TCP/IP and Named Pipes'. ... under the default settings SQL Server does not allow remote connections. ...
      (microsoft.public.dotnet.framework.adonet)
    • Re: MS SQL 2005 Configuration ???
      ... It sounds like you are running SQLExpress, not SQLServer. ... I don't have SQL Express, so I can't replicate what you're seeing. ... "Surface Area Configuration for Services and Connections", ... SQL Server Browser). ...
      (microsoft.public.dotnet.framework.adonet)
    • Re: SSIS as part of scheduled job fails
      ... Can't even open the package. ... Deloyed to SQL store. ... Microsoft SQL Server Management Studio ... Encryption not supported on SQL Server. ...
      (microsoft.public.sqlserver.dts)
    • Re: SQL Server 2005 Express Connection
      ... Some people have been having issues when trying to make remote connections ... networking protocols are disabled by default in SQL Server Express. ...
      (microsoft.public.sqlserver.connect)
    • Re: SSIS as part of scheduled job fails
      ... Can't even open the package. ... Microsoft SQL Server Management Studio ... Encryption not supported on SQL Server. ...
      (microsoft.public.sqlserver.dts)