TurboDB Engine Documentation
Data Security
See also
Previous  Top  Next


Normally your TurboDB database tables can be opened by any person who has access to the file and who uses a tool that can read TurboDB database files. To prevent people from doing so you can define a password for your tables. All TurboDB tools respect this password and will not show the content of the table unless the user has entered the correct password.

While this is a very useful feature in many cases, it is not a true protection for your data. Like in other file-based database engines (e.g. dBase, Access, Paradox) TurboDB stores your data in the database files directly. This means that you can read the content with any binary editor or even a text editor. This is also true if you assigned a password to the table, because the password does not change the way database values are stored. If you want to secure your data from being viewed by unauthorized people TurboDB Engine offers a very fast encryption algorithm, that encrypts every record when it is written to the file. In addition to the password you can assign a 32-bit key to each table that is used for this encryption. As you might know a 32-bit key in our days is not secure enough to do banking or other high security things. But for most applications this level of security is appropriate and a shorter key speeds up database transactions.