Quote:
Originally posted by janrif
So, in essence, what this trick does is to allow me to open a password protected file. And yes I understand that just because I'm working from a template, it's sort of automated.
But I could just as easily have a second password file, switch to whenever I wanted to add a private item & switch back to my master file. Closing that second file would encrypt the data as well.
I think -- as clever as this might be -- I don't get the convenience of this approach. That's what I'm trying to understand.
|
Ask yourself, why do I want password protected item in THE PARTICULAR database?
Of course, you can have dozens of encrypted files spread somewhere on your disk, ... then you dont need UR
The whole point of PIM is to gather and concentrate your data, and be able to retrieve it fast ... so the advantage of the approach explained above is, that your have your data embedded in the given database, and can easily create protected items inside it!!!