Hi Dan!

Thanks for the info! Hmmm...what if I don't use menus in my application? This would not be good. And actually, it makes a lot of sense to use security at the form level. For instance, I have an employee table that can only be looked at, printed, maintained, etc. by a manager-level user. When the user clicks on the button (I load my maintenance type forms from a form that has lots of buttons on it) to load the employee form, it shouldn't load period unless the user has manager-level access! This should not be a problem, I would think? But, then I've been wrong before .

But, you have given me a work-around idea...putting security on the buttons. This is more work, since forms are called from multiple places.

What appropriate methods are missing? I see the icontrolid property at the form level.

Thanks again Dan!


>Hi Scott.
>
>I still work with the MM application that security and language was originally designed for. I have also created at least one other MM application that has security enabled. From what I recall, form security isn't implemented at the form level. I looked and couldn't find the appropriate methods at the form level. The way to implement security at an entire form level is do it at the menu pad level. If you think about it, setting a form to Read-only doesn't make a lot of sense since all controls would be read-only thus all buttons would be disabled etc.
>
>Try implementing security on just one text field and see if that works for you.
>
>HTH
>
>-Dan
>