Domino 9 und frühere Versionen > ND6: Entwicklung

Notes-Fehler 0c:16

<< < (3/3)

just.do.it:
Hallo,

wo wir schon beim Thema "seltsame Phänomene " sind.  ;) Das komprimieren des Arbeitsbereiches wirkt auch manchmal Wunder.  ;D

Gruß
Dirk

Barbara:
So, ich habe den Fehler eingegrenzt.
1. Er tritt nur bei 6.5.5 auf.
2. Jetzt muss ich etwas ausholen. Diese Dokumente sind unter bestimmten Bedingungen nicht bearbeitbar (Querymodechange). Da viele User das Objekt zum Bearbeiten öffnen ohne sich zu vergewissern, dass sie im Editmode sind, schaltet der Button automatisch um. Und durchläuft dabei den Querymodechange. Ist das Bearbeiten verboten - voilá kommt der Fehler.
If uidoc.EditMode=False Then uidoc.EditMode=True
If uidoc.EditMode=False Then ......

Jetzt muss ich erst mal in mein stilles Kämmerlein und nach einer Lösung suchen.  >:(

Danke für's mitdenken

Barbara

Barbara:
Ich habe die Bedingungen für das Bearbeiten in den Button mit eingebaut. Wenn jetzt die Aufforderung zum Umschalten kommt, läuft der Querymodechange ohne Abbruch durch und die Fehlermeldung bleibt aus. Getestet auf 6.5.2; 6.5.4; 6.5.5; 7.0.1

Gruß
Barbara

eknori:
Antwort steht in der KnowledgeBase:


--- Zitat ---In IBM Lotus Notes Client 6.5.5 the following error occurs when a user is working in a Notes document:

"Notes Error - #0C:16".

The user may be opening the document, recalculating it, sending it, saving it, closing it, etc.  Whether the document was originally opened in Read mode verses Edit mode may affect whether or not the error is observed.  This issue was not observed in prior 6.x releases of the Notes Client or 7.x releases of the Notes Client.

The issue occurs in cases where the form's QueryModeChange sets Continue=False, and another form event is coded to change the Edit mode via LotusScript using the EditMode property (of the NotesUIDocument class).  The issue can be observed in cases where EditMode is being set to True or False depending on the sequence of steps.

The error does not actually trigger when the code Continue=False is executed, but actually when the flow of control passes back to the event which set the EditMode property.

A basic example that demonstrates the issue is below.

Given a form that contains the following code in the events noted:

Sub Postopen(Source As Notesuidocument)
   Source.EditMode=True
End Sub

Sub Querymodechange(Source As Notesuidocument, Continue As Variant)
   Continue=False
End Sub

If you create a document with the above form, save it and close it, and then re-open it in Read mode the error will occur.  If the PostOpen event set EditMode to False then the error would occur in cases where you opened the document in Edit mode initially.

--- Ende Zitat ---

Lösung:


--- Zitat ---This problem was reported to Quality Engineering as SPR # MFOE6E8STJ, and a fix is being researched.

A cumulative client hotfix (CCH) is available for Notes Client 6.5.5 that fixes the issue reported in SPR# MFOE6E8STJ.  Since hotfixes do not receive the extensive testing that maintenance releases and fix packs do, customers are encouraged to implement workarounds until this fix is in a generally available release.  However, if workarounds are not possible and you still need a fix, please contact IBM Technical Support to request the CCH containing the fix for this issue.

Workaround:
Rather than performing conditional checks designed to halt a mode change within the QueryModeChange event, you can design similar checks within the events that are setting the EditMode property such that they avoid setting it when undesired.

For example, if the QueryModeChange event contained a conditional check:

If <condition> then
  Continue=False
End If

Then remove the above code and apply the same logic to the event setting EditMode:

If Not <condition> Then
  source.editmode=...
End If

--- Ende Zitat ---

Navigation

[0] Themen-Index

[*] Vorherige Sete