× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



One good approach I read somewhere, is to put the last 4 digit of SSN in the original file and use a secondary file joined by primary unique key, to hold the encrypted fields.

Here is also a problem I have seen. The SSN# being the primary unique key of the file and used to link other tables. Time to redesign your database. But you can make it work by using a one way encryption scheme. That is where the data is also the key. You enter on to the screen the SSN#, (By the way it can be any data not necessarily a SSN#), Encrypt it before performing the DB lookup, and use the encrypted data as the key. The data cannot be decrypted, easily, but you can still retrieve the record if you already know the SSN# in this example.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.