Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Security / September 2005

Tip: Looking for answers? Try searching our database.

MS Access linked tables SQL Server

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
John - 20 Sep 2005 23:00 GMT
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
Mary Chipman [MSFT] - 22 Sep 2005 21:20 GMT
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

>Hello,
>
[quoted text clipped - 8 lines]
>
>John
Noone - 23 Sep 2005 16:02 GMT
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)

> What do you mean by "secure"? When that term is used in conjuction
> with Access, the word "oxymoron" usually follows :-) First of all, the
[quoted text clipped - 25 lines]
>>
>>John
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.