OK, one last update on the issue that Erik Brooks brought up a couple of weeks ago.  Chad Scott, who has worked this issue diligently in Lotus Support, reports:

A new Technote has been released to document the history and fix for the issue Erik Brooks blogged about last week. In short, there was a regression caused by a fix in recent releases that could cause existing code to return an error where it previously did not. With the new fix, this no longer occurs and the fix for the original problem with future-dated views is preserved.
I have heard directly from a customer that the fix is not only good but better, and Erik Brooks alludes to this in his Thursday night "8.5.1 unfail!" update.

Link: Chad Scott: LotusScript and Java functions can return "The collection has become invalid"... >

Post a Comment

  1. 1  Nathan T. Freeman http://nathan.lotus911.com |

    I'm amused that Erik officially has a bug named after him now.

  1. 2  Erik Brooks  |

    @1 - Yeah, me too. I'm right up there with Russ. ;-)

  1. 3  Gerrit Schut  |

    I just don't understand why I need to start a support ticket to get the fix...

  1. 4  James W. Stuart  |

    Shame that the fix has now been recalled, is not in the just released Fix Pack 2 for 8.5.1 and won't now be fixed until May, when Fix Pack 3 comes out :-(

    { Link }

    "Hotfix Recall: SPR CSCT836HFL - LotusScript and Java functions can return "The collection has become invalid" when accessing frequently updated views plus clarification on who needs this fix"