Leaderboard

The reason is elsewhere: the SEE (SQLite Encryption Extension) is payware and the possibility to use system.data.sqlite using the very same API made it possible to get encryption for free. The SQLite team has to earn some money to maintain, enhance and expand one of the most used free piece of software ever. They decided to drop free encryption from the system.data.sqlite bundle. Note that the whole SQLite codebase is public domain so there's nothing preventing you or anyone else to add the encryption layer of your choice to your derivation, modulo you know exactly what you're doing!

You can use an encrypted SQLite database by using a version of system.data.sqlite.dll <= 1.0.112.0 as more recent releases drop the encryption layer. Alternatively you can use any release of sqlite.dll and place the database on an encrypted volume/directory. Then access protection and password management is pushed back to the OS, making your life simpler as you noted. There are many advantages from using such a database: o) zero installation or maintenance required o) everything can be embedded inside your application o) the RDBMS engine gives you ACID properties for free o) it's powerful, fast and secure o) you can easily refactor your design, should your needs evolve over time o) it's portable accross any platform o) it's very well documented o) ...

For a bit more complex storage I would use JSON There are a few JSON UDFs, you can use them to create JSON objects and manually read/write them to your files. If the storage is more like a database I would consider SQLite, which is supported by the official UDF in AutoIt

It's best not to make your own password manager, it is incredibly hard and time consuming to patch all the holes... not counting the effort you'd need to go through to make it usable, especially outside Windows computers, like your phone. Just use KeePass, it's a secure and open-source password manager with all of the features you'd need, there are clients for Android and the main program itself is cross-platform. If you want to store files in a secure way, try VeraCrypt (TrueCrypt's defacto successor).

Here is fix for my last script, there was badly filled Rect structure: Original bad code: Global $RichEdit_pos = ControlGetPos($Main, '', $Edit) Global $RichEdit_Rect = DllStructCreate($tagRECT) DllStructSetData($RichEdit_Rect, 'Right', $RichEdit_pos[2]+25) DllStructSetData($RichEdit_Rect, 'Bottom', $RichEdit_pos[3]+25) By coincidence this bug wasn't problem here because Left/Top position of RichEdit is 24/24 and I used +25/+25 as correction mistakingly fo width/height of Scrollbars. You can test it, problem occurs when you increase RichEdit's X position (X=24 -> X=34). Correct fix is this: Global $RichEdit_pos = ControlGetPos($Main, '', $Edit) Global $RichEdit_Rect = DllStructCreate($tagRECT) DllStructSetData($RichEdit_Rect, 'Left', $RichEdit_pos[0]) DllStructSetData($RichEdit_Rect, 'Top', $RichEdit_pos[1]) DllStructSetData($RichEdit_Rect, 'Right', $RichEdit_pos[0]+$RichEdit_pos[2]) DllStructSetData($RichEdit_Rect, 'Bottom', $RichEdit_pos[1]+$RichEdit_pos[3]) With this fix RichEdit will be correctly repainted (including its H/V scrollbars) no matter of it's position inside main window.