So, the other day, I blogged about a problem with ComputeWithForm in LotusScript. Many of you feel that ComputeWithForm was the hack, rather than the workarounds, which is fine and dandy. However, if you have an application that already uses ComputeWithForm and you’re having issues, head over to Julian’s blog to get the tool he created to help find what is causing the failure.
An interesting note, I used the tool and found that I was getting an error on a field that had the following (admittedly poorly written) @Formula in input translation: @Date(@ThisValue). Of course, the formula should have been: @If(@thisvalue = “”; “”; @Date(@ThisValue)). However, the first formula still worked on the front-end document. If the field was blank, the doc still would refresh and save without error. BUT, if the field was blank, it was causing ComputeWithForm to fail. I was able to discover that, thanks to Julian’s ComputeWithForm tool.
My original problem had nothing to do with the field I wanted recalculated, but another field altogether.