Defines the access that all users, including you, have to your application database.
Syntax
dbrstrct database-name
database-name
The name of the database for which you want to restrict access.
Notes
Before you define database access, it is very important that you make a copy of your application database and precompile all of your application procedures against that database. For example, suppose you do not precompile a procedure that updates the database and then you deny update access to the database. You will be unable to compile that procedure against the newly restricted database.
Keeping a copy of the unrestricted database also lets you redefine the database restrictions at a later time. To redefine database restrictions, dump the data from the restricted database, make a copy of the unrestricted database, define restrictions on that database copy, and reload the data into it.
Example
Sample DBSTRCT command:
dbrstrct mydb
As you can see from the options listed in the following image, you can define access globally, for all files, or you can define access on a file-by-file basis. Any restrictions you define affect all users, including yourself.
Figure 21. Database Restriction Utility
If you choose option 1 and deny update access but permit query access, no users, including yourself, will have update access to files or fields in the database, unless that update is being done by a procedure that was precompiled against the database before the database was restricted. However, all users will be able to write procedures that query the database.
Before you define database access, it is very important that you make a copy of your application database and precompile all of your application procedures against that database. For example, suppose you do not precompile a procedure that updates the database and then you deny update access to the database. You will be unable to compile that procedure against the newly restricted database.
