Shawn,

>Exactly! I would like non as well this way I can build my menu off of this setting as well.
>Menu level has visible Access to the menu item if the user has Read-Only or Full Access, I f security has None then user would not see it on their menu.

Have you considered how you would implement this? You'd probably have to create a subclass of MenuItem in order to make this happen (we've avoided that so you can still use the VS .NET menu designer). At the time a menu item is created it would have to know what the security setting of the associated form is (which would in turn require it to know the unique ID of the form). Although this COULD be done, it's not something that could be done at the Framework level. You might want to simply use the built-in functionality for setting access to None on the menu item itself.

>Form level, Allows me to set a series of common objects as read-only, or none or full.
>But I would still like the option of setting the fields independently.

What WOULD work, is the ability to set a form to read-only and have all controls respect that setting. A new property would have to be added to all controls to specify that they should ignore form-level security.

As far as having a SET of user interface controls respond to the same security setting, you can do that right now by setting all controls in the group to the same Control ID. You can do this in the builder by selecting all controls and setting the ControlID through the builder. All controls would then have the same GUID.

At any rate, I'll add this to the list of items to consider for the next version.

Regards,