Data Encryption Issues with ADP and SQL2005

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am new to the arena of Access 2003 and ADP. I am converting an Access DB
and application to ADP and SQL 2005. As a test I created a DB on the SQL
2005 remote (not on my LAN) server and then created a new ADP in Access that
links to it. I see the tables OK and can operate on them just fine so far.
I have opened the tables while looking at the network traffic with Ethereal
and it seems the data is encrypted as it transfers from the server to my
workstation. The target application contains sensitive information (social
security numbers(SSNs) and credit card data). Here are my questions.

1. Is the transfer of data, login passwords and table contents, normally
encrypted as a matter of design for an ADP? If so, are there any special
caveats?

2. How is the issue of data storage of sensitive information, like SSNs, to
be managed in the context of an ADP? SQL 2005 has functions like,
EncryptByKey, to manage encyption.

Thanks for your help.

Eagle
 
dude dont use SQL 2005 for your first ADP. it would just be brutal.

tell us more about your requirements.

I am pretty sure that you can force encryption in plain old sql 2000
and access 2003.
I believe that it's just a simple setting under file, connection,
advanced

-aaron
 
Back
Top