Encryption is enabled by setting the session object $encryptkey property before logging on to the SQLite datafile. $encryptkey accepts a string of hexadecimal characters, which should be of even length and should be no longer than 32 characters (the key value will be truncated if it does not meet either of these criteria). The accepted key value is then used to seed an internal private key which is subsequently used by all statement objects belonging to that session object.
To create a new encrypted datafile, the $opencreate property should also be set to kTrue before logging on. Once encrypted, $logon() will fail unless the correct $encryptkey is supplied. $encryptkey will be ignored (cleared) if the DAM detects a connection to a non-encrypted datafile.
The encryption function in the SQLite DAM is enable using two new methods: $encrypt(filename) opens a non-encrypted datafile and encrypts it using the $encryptkey, while $decrypt(filename) opens a previously encrypted datafile and decrypts it using the $encryptkey.
For more details about SQLite encryption in Studio 8.0.3 see the ‘What’s New in Omnis Studio 8.0.3′ manual available here: http://www.omnis.net/products/studio/whatsnew.jsp