Ian,
I think for my purposes simply encrypting the DATABASE itself would
be better. Basically the only encrypted database will be one of
serial numbers and preferences. I don't really want to go through
the trouble of converting/encrypting each individual entry; not to
mention managing a seperate array. I realize that the DB would be
decrypted while working, but it would only be referenced for very
very very short periods of time at the beginning of any piece of
software's run to make sure they have a valid serial number, etc.
Any suggestions for this? If not, I'll still take any input you have
that would make your previously proposed method "easier". ;)
Thanks so much,
Michael
On Mar 11, 2006, at 1:00 PM, realbasic-nug-
[EMAIL PROTECTED] wrote:
It works OK for "select columnx, columny... from table_name where =20
columnz =3D"nnn"
provided that columnz is unencrypted. Given that you have designed =20
the database yourself you can make the "nnn" data in columnz fairly
=20
innocent data and you know from the design what is in the other =20
fields. It makes for some awkward array management in memory and
you =20
must remember to dispose of these structures when you are done with
=20
them (regardless of any garbage collection!) but it works OK.
Ian.
--
Dr Ian M Piper
[EMAIL PROTECTED]
skype: ianmpiper
--
Where is the wisdom we have lost in knowledge?
Where is the knowledge we have lost in information?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
