I have been working on these issues for over a month, and have only managed to get a global issue pared down to an issue involving a handful of users. I cannot rest until the issues are resolved for all. The users won’t let me.
This is an older application, probably begun in V4, running without major incident through V5 and for a few months in V6, until the company added a new domain. The app gives users Default Author access through ACL, and Authors/Readers field control their access to documents they create. This was not happening for the new domain users; they could not see or edit their own documents despite proper inclusion in the Authors/Readers field. After some research, I recoded the computed Authors/Readers field to ensure that they ALWAYS used the canonical name, not the Common Name that had been used from V4 onward.
That appeared to clean up the new domain problem, but also appears to have introduced a new problem. Users of the OLD domain, for which Authors/Readers had always worked before, are now suddenly unable to edit their own documents.
The fact that they can READ their documents tells me that at least the Readers fields are working Complicating this is that there is a controlled Access section in which most if not all the editing should be taking place. So it’s entirely possible that the problem that’s preventing them from editing is within this section, not the document itself.
I have ensured that the affected user’s full Canonical Name is in an Author’s field (which reports itself as READ/WRITE-ACCESS NAMES as it should) AND that the user’s full Canoncial Name is properly in the Who Can Edit This section of the controlled Access section). The affected users still cannot put the document into edit mode. I have even put in test code to wit: source.editmode = TRUE; if source.editmode <> TRUE then msgbox “Not in Edit Mode” end if. These users always get the popup “Not in Edit Mode”, which other users with the same access do not.
Is there some issue with using Authors/Readers fields and controlled access sections in the same document that would suddenly become a problem in V6, and ONLY for a few users? I could use any and all suggestions I can get, any keywords I could try to search further, any life preserver that anyone can throw.