"Attempt to execute nested form events" - but no call to SelectAll

Unlike other posts that see this error, I have no .SelectAll statement or OnFocus code. Like the other posts, the problem manifests itself only after opening a document and then clicking on the “Edit Document” action button. The order of events is:

Sub Querymodechange … (Nothing of merit happens here)

Sub Entering(Source As Field)

fieldName$ = uidoc.CurrentField    



Call uidoc.FieldSetText ( "nLineStep","0" )          

Call uidoc.FieldSetText( "cHoldStatus",uidoc.FieldGetText(fieldName$))          

End Sub

Sub Postrecalc … (Empty so don’t know why it was even entered)

The messagebox “Lotus Notes, ! , Attempt to execute nested form events., OK” appears. This seems to be the bottom of a stack and we now work our way back up, calling each subroutine again as we go along.

Sub Postrecalc … (*Still empty but here we are again. On the next iteration of testing, I deleted the null contents to stop it being called. I NO LONGER GET THE ERROR WHEN IN DEBUG BUT DO GET THE ERROR WHEN RUNNING OUT OF DEBUG!!! *)

Sub Entering(Source As Field)

fieldName$ = uidoc.CurrentField    



Call uidoc.FieldSetText ( "nLineStep","0" )          

Call uidoc.FieldSetText( "cHoldStatus",uidoc.FieldGetText(fieldName$))          

End Sub (But this time (before deleting the Postrecalc Sub) the first line of code is skipped over. After executing the last FieldSetText (stepping through in Debug), I do see a screen blip - from setting the field?)

Sub Postmodechange … (was empty so I deleted it and it is no longer called)

So, has anyone heard from the other posts heard from Lotus Development about a fix? Does this happen on R6 versions after 6.0.2 CF1? Has anyone fixed a problem like this?

Subject: “Attempt to execute nested form events” - but no call to SelectAll

I was getting this error despite the fact that so SelectAll code was running, and finally traced it to the fact that I had a couple of editable fields at the top of my document which both had entering events which moved the cursor to the next field. The idea being that the cursor would end up in the first “real” editable field, which may or may not have the “default focus” attribute.

Anyway, there also happened to be another, hidden, editable field between the top two fields and the “real” editable field, which should have had no effect on anything since it was hidden. Nevertheless, the problem went away simply by making this hidden field computed instead of editable.

Running a 6.5.1 client.

Kevin

Subject: RE: “Attempt to execute nested form events” - but no call to SelectAll

Debug mode has some differences in its interaction with the client UI. I suggest you insert debugging code such as shown here to try and find out where exactly the problem is occurring.

Differences in debug mode operation can also indicate an order of compilation issue. Any script libraries need to be compiled before the script that calls them. Use Recompile All LotusScript in Designer.

Your Querymodechange code might well be relevant. There are many ways this particular error can occur – it doesn’t have to involve a field entering event. Anything that results in the recursive invocation of a form event will cause this.