These are the security measures provided for your DP4 application:
You can specify that you want the data in a table to be encrypted, to make sure that the information cannot be easily read except under the control of DP4. The encryption algorithm is designed for speed rather than ultimate security. It protects against the casual hacker, but not against professional assault. (If you are concerned about this aspect of security, then from 4.622, you should also use Enhanced Data Compression, as the data is then stored in a format which would be extremely difficult for other software to decode.)
You can restrict user access to the database, at table and field level using the DP4 access control facility. To hide a table or a field from a user, you give it an access level higher than that of the user (or group of users). Alternatively, you can allow a user to see a table, but not to change it, by changing the write access level. Users have read and write access levels between 0 and 99
You can assign read and write access levels to a menu option to restrict access to a program. You can assign access levels to your QA Build Programs to restrict access from the menu or the command line
You can ensure that users cannot change QA Build programs by using a 'Conceal' option that hides the program code