I’ve encountered two repeatable problems with Notes 6.0.1 when using computed text, problems that @IsError doesn’t protect against. I’m curious if anyone else has seen this.
I’m working with long-existing documents. If I edit a computed text instance, put in @Formula, and somehow introduce a code error, then Save, Notes 5 just displays the error message and/or respects an @IsError to display something else. However, Notes provides a generic error message, then immediately crashes – it closes itself, with no RBOD. Rebooting is usually require.d
Two examples:
#1: @DbColumn in a computed text field inadvertently returns more than 64K of data. @IsError is there to trap errors, and it works fine when Domino displays the document on the Web, and when the document is opened in Notes 5. But in Notes 6.0.1, simply saving the document crashes Notes…every time! Notes tries to execute the code, gets the error, ignores (or never gets to) the @IsError, and crashes. At first I thought this meant @IsError is flakey, but then I encountered the next example. (Modifying the @DbColumn target view to contain less than 64K doesn’t trigger an error so Notes doesn’t crash.)
#2: I put @Environment into a computed text field to get a value from notes.ini, but the desired value doesn’t exist. Saving the document causes Notes to crash and close; reboot is needed. I didn’t get to the point of adding @IsError (I just wanted to see what @Environment would return), but I’m guessing it won’t help.
In both cases, the Save works – reopening the doc shows the last-saved code. So the crash happens after the Save, when Notes tries to then execute the computed text code and update the displayed document.
The problem happens in Notes, not Designer, because only Notes tries to immediately execute the formula.
Has anyone else run into this?