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