View Single Post
  #14  
Old April 15th, 2008, 10:27 AM posted to microsoft.public.access.forms,comp.databases.ms-access
Les Desser
external usenet poster
 
Posts: 45
Default Advice on securing a sensitive Access database

In article
,
" Tue, 15
Apr 2008 00:23:40 writes

I also found the code for the GUID creation, courtesy of Trigeminal. I
have used this in Excel and Access before and it seems to work fine :-)


Thank you.

I have read trough your first post again and am having some difficulty
understanding it all.

It would be helpful to get an overview of what is being achieved.

For starters, is the following correct?

1. Relevant tables in the data mdb are individually encrypted by
encrypting each relevant field.

2. Decryption keys are stored, encrypted, in the front-end db (does it
have to be separate from the application front-end?)

3. Access to the decryption keys is controlled by some user entered
password.

4. It seems obvious that any field that has been encrypted can no
longer be directly bound to an Access control. It must be displayed via
a function and updated by code.

Point 4 is not a problem as it is only limited data that needs
encryption.


--
Les Desser
(The Reply-to address IS valid)