SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a custom solution, which has multiple related lists. Four of the Lists have a lookup field based on the field of one list. And, that list has a lookup based on the field of another list.

So, if the user deletes one list. It will break the functionality. How to stop the user from deleting those lists?

And, also if the user modifies the field value which is being looked up in other lists. How best to reflect the change in all the other lists.

Looking forward to your replies :)

share|improve this question

Give users read permissions to the lists so that the values can be read when creating list items. Only give a select few people contribute and full control.

Edits to the lookup values will get replicated to all items holding those values. It's one of the nice features of lookup columns.

share|improve this answer
Thanks Eric, unfortunately I do not have control over who has access to the site. It is an internal portal and a lot of individuals have full control access :) – goso Oct 29 '11 at 11:18

If you cannot change permissions, I am afraid there's not much you can do.

This is "fixed" in SharePoint 2010, with additional options that retrict deletes on the lookup list.

share|improve this answer
Thanks Christophe, I would raise this going forward :) – goso Nov 2 '11 at 21:28

Tell the users that deleting or modifying those lists puts them in an "unsupported state", then refuse to support them.

It may sound counter-intuitive, but establishing this expectation among your users will pay off in the long run.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.