I have an in-house written CRM database which includes a contacts form. This form was based on the standard Lotus person form in pernames.ntf (R5) and is more or less identical but with some extra fields specific to the application.
Since the database is shared and for security reasons all general users are "Authors" in the ACL it was necessary to make sure the various protected fields e.g. LastName, MailAddress, FullName etc, were modified so that the protection was turned off (Field properties, untick "Must have at least Editor access to use").
The problem I have is that for some people and not all, these settings are ignored and whenever they create new contact docs in the database the fields are set as protected. This means they can't subsequently edit those fields because they are only Authors in the ACL.
Most users have a local replica of the db so they can work with it offline. I found that if a user created the contact doc on the server db the fields were unprotected correctly but after replication and opening the doc on their local replica the fields WERE protected! I have made sure they have the absolutely current contact form design version (by making a visual change to the form and replicating this and seeing that this change is visible to them) and this makes no difference. The fields are protected when local but show unprotected on the SAME doc in the server db. Weird!
Theorising this suggests that field properties are not necessarily stored within the db doc itself and are perhaps cached?
Does anyone have any ideas on this or have seen this behaviour?
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!