So I do NEED my users information to be securely encrypted.
In which case the operator will need to identify himself to the program every time he uses it, i.e. authenticate himself and establish his authorisation. It is emphatically /not/ possible to hide a decryption key in a binary or in the registry etc.- which was the gist of the other thread.
And in my bit of research I found several articles that claimed SQLite3 may have some serious security vulnerabilities which was just one more factor that moved me away from it.
Which are probably less severe than those any one person in this forum- me, you, or anybody else- would inadvertently build into something written from scratch.
And to be honest... i did some tutorials using SQLite3 and it truly seemed a bit overkill for what I am doing.
I think the bottom line is that if you're writing something which allows for data to be modified as well as merely appended then it's worth using something like SQLite.
MarkMLl