Modify a RTF field . Refresh it - Strange behaviour !

[Toma Bogdan]

I want to have a rich text field to add comments to while protecting
what is already in there without changing user access control or
redesigning the database.

It works like this (with 3 fields):
1) Computed rich text field, CommentsDisplay with formula Comments
2) Rich text field, Comments, which does not show up on form at all --
it contains previous comments
3) Editable rich text field, NewComments -- where th user add his
input and attach docs

and the code in the PostSave form event :

Code

Sub Postsave(Source As Notesuidocument)
Dim mainDoc As NotesDocument
Set mainDoc=Source.Document
Call mainDoc.RemoveItem( "CommentsDisplay" )
Dim rtitemA As Variant
Dim rtitemB As Variant
Set rtitemA = mainDoc.GetFirstItem( "Comments" )
Set rtitemB = mainDoc.GetFirstItem( "NewComments" )
Call rtitemA.AppendRTItem( rtitemB )
Call rtitemB.Remove
Call mainDoc.Save(False, True )
End Sub

but it is a strange behaviour:

step 1: I create a new doc
step 2: I put the string "1" in the NewComments field
step 3: I save the doc
step 4: when I open the doc :
Comments field "1"
CommentsDisplay field nothing
NewComments field nothing
step 5: I put the string "2" in the NewComments field
step 6: I save the doc
step 7: when I open the doc :
Comments field "12"
CommentsDisplay field "1"
NewComments field nothing
step 8: I put the string "3" in the NewComments field
step 9: I save the doc
step 10: when I open the doc :
Comments field "123"
CommentsDisplay field "12"
NewComments field nothing


Why the field CommentsDisplay which had a computed formula doesn't refresh on doc open ?!? (it is with a step backward than Comments field ...) ?

[Rob Green]

jez..

just a try:
use the field comments and newcomments
make comments > computed => on field comments itself

then your script and all seems ok now...


And what about the commentsdisplay field?
...i´m not too sure with computed RichText field types, but take a look at the field values in the read mode ... the rt field "comments" is twice there.."comments" and "comments"! Containing the old values in "one" field and the newest values in the "second" field. So, this could be the explanation that commentsdisplay is always one behind.

[Toma Bogdan]

The Comments field keesp the last inputs of the users to prevent them to modify something ! I display this information into CommentsDisplay field and after they write something in the NewComments field I add this field to the Comments field !

Here is the sample Notes database (zipped) !

[Rob Green]

ok, i think i understood it ..

but, once again: the problem is - im very sure about - , that the commentsdisplay field is related to the comments field, which exists twice after the first save.

1. creation of doc
entering AA
2. saving first time
3. read mode: 2 (!!!) fields "comments" in the field list>
first  "comments": AA
second "comments" : empty
4. edit doc
entering "BB"
5. saving
6. again two comments fields
first "AABB"
second "BB"
....

see what i mean?
Commentsdisplay always shows the right field, but which one of both ?  

[Toma Bogdan]

I suppose that you saw the sample ! I belive that it is a simple solution ... but what is that solution  

Regards

[Rob Green]

at the moment i have no idea...its a strange behaviour....maybe take a look at the LN Knowledge base:
http://www-3.ibm.com/software/lotus/support/

enter the phrase "appenditem" e.g.

[Rob Green]

seems to be a bug:
http://www-1.ibm.com/support/docview.wss?rs=475&context=SSKTWP&q=computed%2Brich&uid=sim1d37dd1d35bcd5991852566860064271f

[Toma Bogdan]

again a Notes bug ... maybe in R6 it will not be the same  

but how can I restrict the user to modify the last posts.... just to see what he had post .... and the user to have the permisson to add other comments to this field ?

i am a little confused now ....

[Toma Bogdan]

at this address http://www-1.ibm.com/support/docview.wss?rs=475&context=SSKTWP&q=computed%2Brich&uid=sim1d37dd1d35bcd5991852566860064271f I saw that they reffer to the .... Software version: Notes 4.x  

but the reality is other .....

[Rob Green]

if it would be fixed, the doc would see an update...but there is none  

ok, anyway:

1. Field:
NewComments
RT, editable

2. Field:
Comments
RT, computed
Formula: comments
(so computed in itself)

3. Youre LS Code

4. It works perfectly, without the third commentsdisplay field

Now, you can enter any comments to the first field "newcomments", saving it, whereas with every postsaving procedure the entries are logged to the comments field, which indeed is computed, therefore not editable afterwards. I still cant see the need for a third field.

[Toma Bogdan]

let's check this  

[Rob Green]

im a little bit curious...how does it come that you´re posting on a german board instead - seems easier to me, not that you think you´re not welcome  - on notes.net e.g., full of english speaking freaks?

[Toma Bogdan]

the code works like before.... as I said .... if I leave the code like this the user can modify and delete the whole content of the Comments field !

So if I use the CommentsDisplay field the user can't modify the Comments, he can saw the initial content of this field through the CommentsDisplay field and he can add some contents to this field through NewComments field!

[Toma Bogdan]

I work a lot with notes.net   but it seems that the english speakers on notes.net are little lazies   so I use this amazing forum (you and others like you are the reason that this forum is amazing) ! The Notes fan are everywhere  

[Rob Green]

the code works like before.... as I said .... if I leave the code like this the user can modify and delete the whole content of the Comments field !

There must be a mistunderstanding between us. How does the user can "delete" the contents of the "comments" field, since its computed in itself and not editable??

If you mean really this:
User enters in newcomments:
"We are Borg"

becomes after saving:
"we are borg" in comments (computed) AND
"we are borg" in commentsdisplay (editable in your version..little bit confusing for the user, dont you mean?)

now user edits doc by entering a new comment in "newcomments" field:
"Resitance is futile"

becomes after saving:
"we are borg resitance is futile" in comments (computed) AND
"we are borg  resitance is futile" in commentsdisplay

So, the field "comments" and "commentsdisplay" serves the same need. One is displaying the log/edit history as an editable RT field and the other as a computed RT field.

My last try: why dont use two fields?
Look here please (im very sure somehow i understand you wrong):

[Toma Bogdan]

it seems that it works... I don't know what was in my head when I try to use a third field....  
thankx !  

[Rob Green]

the big emptiness or big happiness....

ok, just kidding...gratz!!!  

[Toma Bogdan]

thanks a lot .... again, Rob !

Regards