Embedded views, object request not completed....., edit mode

Hello all, I’ve been grappling with some design changes/functionality to the Notes client for R6. These are

  1. Embedded views - I’ve had some users accessing the same document with an embedded view with a show single category property. Some users can see the documents, some don’t. And when the users who cannot see the document goes to another machine and accesses the same document using their ID they can see the documents in the embedded view. Quite strange don’t you think? I am surmising that does an embedded view require machine horsepower just to filter properly? Any similar experiences? Possible solutions? TIA.

  2. Object request not completed because needed access was denied - This error message occurs when the user (who created/embedded an Excel worksheet in the same document using a programmed script) tries to open an Excel worksheet embedded in a document. In my research so far, the only rationale Lotus knowledgebase has come up with is that the embedded object is corrupted. However when the same saved document/worksheet is accessed by her other team members, they can open the worksheet without a hitch. I am thinking that the user who created the document has her Excel app on her machine default to automatically edit the file in OLE. Other people can only open the file in read only state. Any suggestions? Your help will greatly be appreciated.

  3. Finally (uidoc.EditMode) - A script has the following code block

If Not uidoc.EditMode Then

uidoc.EditMode = True

End if

The intention of the said code block is to check if the user has edit access, which in my opinion is bad Notes programming. Any ways, the point I’m driving at is in R5 if the user comes accross the code block and tries to put the current doc in edit mode, the script throws an error and displays it and exits. In R6 though the error is not thrown at this point and the script proceeds through. However, the document changes in script are invalidated when the doc.Save is called and the same error is displayed. Why doesn’t the client throw the error at the line uidoc.EditMode = True? Has the client or property behavior changed between versions?