>>>>I was referring to my earlier message that DBFs are not secure. You can do tricks to work around any problem, but trying to make a DBF secure is like converting a bicycle into a car. Why bother, when there are far better solutions. Especially now that DBFs will die sooner or later, I assert that using a "real" database server for storage is the best way to go.
>>>
>>>I'd really appreciate if some day everyone could just listen to the OP needs instead of invariably say:
>>>"go my way, it's the best and there is no other".
>>>
>>>Forums are meant to share ideas rather than impose one's ideas or beliefs.
>>>
>>>"YMMV"
>>
>>When I see someone driving against i cliff, I advice them to either break or change the directions. It's their choice to listen to my advice or not, and that's why I don't bother to discuss this any further.
>
>
>The OP is not driving off a cliff. That is just another false comparison. The OP has an existing app. which he wishes to enhance with seamless encryption / decryption without re-writing his app. - read the original post.

I have. As I wrote earlier, you can't convert a bicycle into a car. But if a bicycle will do, a bicycle will do. However, you still will ride without airbags.