Jump to content

Locking RF fields?


Recommended Posts

Delmer,

If user A sends a file to user B who makes their specific changes to objects with attached records as part of a group effort and then returns it, how are you to determine in which respects the file has changed so as to screen out data fields that should not have been modified?

User A could split the RF into multiple parts to segregate fields that should not be changed but this may cause a significant inconvenience to the operations of user B.

Setting a field to read-only would allow full sharing of tasks while also maintaining data integrity.

As it stands now, any member of the group can change any data and no one will know.

Joel.

Link to comment

It sounds like you might be better off having each user work in his/her own file and using Work Group Referencing to tie everything together. That way, user A can only "screw-up" his own file.

I don't know enough about your specific work-flow to offer any better suggestion.

Link to comment

Delmer and Travis,

Thanks for kicking this around - looks like some kind of procedural solution is required.

In any DB it's normal to expect some basic level of access control - I'd like to write-protect layers for some users too in some cases so they could see and snap but not modify. Perhaps some of these functions will appear in future releases?

Thanks,

Joel.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...