Another thing occured to me with the field option "must have at least editor access to use". This option can be set and re-set in LotusScript via the IsProtected property of NotesItem. This means that, for example, the Status field could be protected from end user interference but still updated in the WebQuerySave by resetting the IsProtected flag, updating the item's value and then setting the IsProtected flag again. I've just tried it and it works a treat.
This is ideal for my own applications as I never give end users higher than Author access, prefering to use roles to grant access to documents where required.
Another thing occured to me with the field option "must have at least editor access to use". This option can be set and re-set in LotusScript via the IsProtected property of NotesItem. This means that, for example, the Status field could be protected from end user interference but still updated in the WebQuerySave by resetting the IsProtected flag, updating the item's value and then setting the IsProtected flag again. I've just tried it and it works a treat.
This is ideal for my own applications as I never give end users higher than Author access, prefering to use roles to grant access to documents where required.