Simple Access Problem

Hi…

I have a database with two user types…

1: readers (or authors) who must create/edit personal profiles but can only view all other documents

2: editors who, in addition to create/edit their personal profiles can also create/edit all documents (excl. other users profiles)

I’d rather not create roles if possible.

I’m stuck on how to handle in particular user type 1.

I’ve looked at PublicAccess and Author fields but can’t see a fit to above requirement. There must be a simple technique here but i can’t find it…

Should readers be Authors to enable profile editing and i then restrict them editing of other documents somehow?

any advice appreciated.

-Alex

Subject: Simple Access Problem

Both classes of user can be created using Authors-type fields. And what’s wrong with roles? They are, after all, the most appropriate approach to most access problems.

All “normal” users should have Author access to the application. Those currently having Editor access should be assigned a common role (like “[DocEditors]”).

The user profile form should have a computed-when-composed Authors-type field with the formula @UserName. Only that user (and people with higher-than-author access to the database) will be able to edit the user profile.

Other forms should be role-restricted for creation – uncheck the “All Authors and above” checkbox on the security tab of the form, and select the “[DocEditors]” role in the “who can create” list. Place a computed-when-composed Authors-type field on this form as well, and make the formula “[DocEditors]” (or whatever the role is called). That will allow anyone with the role to create or edit these documents while preventing the “readers” from doing so.

Your administrators will normally have elevated access to the database, and will be able to edit and otherwise maintain documents as required.

Subject: RE: Simple Access Problem

Many Thanks Stan… solved using your technique.