[AccessD] Field Level AES Encryption

I tried to send through my hash generator but AccessD rejected it for length.  Basically pick a hash 
and go.  A hash generator takes an input, hashes it, and delivers an output.  The output string is a 
fixed length string that "represents" the input, but you cannot take the output and get back to the 
input.

This really only works if you do not actually need the input for any reason.  Let's say that you are 
storing records where one way you want to look it up is by the SSN.  Actually storing the SSN is 
risky buy by hashing it, the SSN is never stored but you can still get at it by storing the hash, 
and then looking up the hash.

I also use a hash to allow me to compare records.  I hash the address information and store the 
hash.  I can then compare the address hash of one record with the address hash of another record. 
If the hashes are equal, then you have a match.

John W. Colby
www.ColbyConsulting.com

On 4/28/2011 5:21 PM, Asger Blond wrote:
> How do you create the hash - any generator to recommend?
> Asger
> -----Oprindelig meddelelse-----
> Fra: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] På vegne af jwcolby
> Sendt: 28. april 2011 22:10
> Til: Access Developers discussion and problem solving
> Emne: Re: [AccessD] Field Level AES Encryption
>
> Unless you actually need the ssn, I recommend storing a HASH of the ssn.  Then you when you need to
> see if the SSN entered in a form somewhere is equal to the SSN you "stored", you hash the SSN
> entered and compare to the hash you stored.  You never have the ssn stored at all and the hash is
> one way so it can't be deduced.
>
> John W. Colby
> www.ColbyConsulting.com