Welcome to the SQLitening support forums!
Started by Fim, April 26, 2015, 08:18:10 AM
SYNONYM_START: SlSetProcessMods("E0") SLOPEN "ORDKORS.D.DB3" CRYPT_KEY = "1234567890123456" slSetProcessMods "K" + CRYPT_KEY RC = AuxRutsA(2, WORD_PIC, ENCRYPTED_WORD_PIC) IF RC <> 0 THEN CALL ERROR_OUT("AuxRutsA RC=" + STR$(RC)) EXIT FUNCTION END IF SYNONYM_SELECT_STATS: SELECT_SATS = "SELECT * FROM SYNONYMER WHERE WORD =" + $SQ + ENCRYPTED_WORD_PIC + $SQ MSGBOX SELECT_SATS SLSEL SELECT_SATS
Quote from: Fred Meier on August 22, 2009, 10:48:29 AMSQLite does not support encryption/compression of the entire database, nor will it encrypt/compress fields. But since SQLite does allow binary data, encryption/compression can be done by the SQLite using program. By the way, I believe that is the better way since there are so many different ways to do enencryption/compression. SQLtening allows you to store binary data using the slExeBind command. The slExeBind command accepts BindDats. The SQLitening slBuildBindDat command has an encryption/compression routine built-in. You may use these routines or provide your own. See code in ExampleC.In summary: There is no "special" SQLite needed to do encryption/compression. SQLitening allows you to store binary data using the slExeBind command. SQLitening offers you one encryption/compression method. You may roll-your-own encryption/compression method.