A Practical Example

The preceding description of how to set up Controls Security suggests a rather formal process that takes you from a planning stage through implementation. If you find yourself with the need to set up Controls Security for many forms and many controls, we recommend that you follow the process described above.

However, sometimes you may find that you just need to set up Controls Security for one control on one form. If that’s the case, you may find it easier to work the process somewhat backwards. For example, let’s say that while you’re editing a form in the Form Designer, you decide to set up Controls Security for a command button on the form. In this case, you might want to proceed as follows:

1.   Control ID: While you’re editing the form, make up a Control ID for the button and enter it in the button’s cCSControlID property.

2.   Form Name: Make sure the form has a unique entry in its Name property. If the first 12 characters of the form’s name property are not unique among your application’s forms, enter a unique value into the cCSAltFormName property that can be used to identify the form in lieu of the form’s Name property. Enter up to 12 characters.

3.   Control Group Definitions: Display the Control Group Definitions form from the Security Builder menu and add a record for the button. Use the Control ID you created in Step 1. Make up a unique Control Group ID

4.   Control Security Forms: Display the Control Security Forms form from the Security Builder menu and add a record for the form.

That’s it! The next time you bring up the Control Permissions dialog, the form and button will be listed and ready to have permissions granted to users.

More:

Tip - Making a Form Read-Only by User