Buttons don't work with read-only table restriction

Not sure if this is a bug, or I’m doing something I don’t understand.

I have a password-protected solution that is working fine wih no group restrictions set in the security pane (e.g. a user’s group has full access to all tables in the solution).

I want to allow access to all parts of the solution, but for some users I don’t want them to be able to modify any of the data fields. I thought the easiest way to set this up would be to create a group that has read-only access to the database tables, so I did this - creating a new group (ViewOnly) and setting the table restrictions to read only for all tables. I did not modify any form access for this.

When I log into the solution as a user in this ViewOnly group, the fields were unmodifiable, as desired, but all buttons located in the BODY of the solution forms appear to be disabled. The tool tips on these buttons work, but the buttons don’t register a click and the methods do not fire. The methods being called are navigational (e.g. move to another form, form-in-dialog, etc.), and to not cause any data modification. The disabled buttons occur on all forms in the solution where buttons are located in the body of the form (form or list view).

Interestingly, buttons located within form headers or footers function normally, as do buttons on the controller(s).

Any idea what is going on?

BTW, using Developer R2 2.1, on Mac OSX 10.3.5.

I’ve narrowed down the problem a bit and note that button access is disabled only when table update access is disabled. If table update access is enabled, then buttons located in a body of the form function normally even if insert and delete access is disabled.

This is very frustrating and has completely messed up a simple client read-only solution to the data. Has anyone seen this problem or know what I’m doing wrong?

I have same problem.
I think form elements not related to fields (as buttons) should be accessible even if the table is read-only. Grant update is a solution in diplay only form (not editable fileds) but is not very secure, and of course is not appropriate in all situations.

Fixed this behaviour in 2.1.1 for tableview en portalcomponent..
Buttons can always be pressed now. OR the button itself is disabled..

Thanks, Johan. Is there a beta for 2.1.1 available for us to test? - or one that will be released soon? The beta on the developer site is dated 8/30.

I have a cooperator who is anxious to test our solution, but I don’t want to release it until I can protect the data.

Again, thanks for the fix…