FORUM PLAN UPDATE: Date revision: This forum will remain open to new posts and responses until December 1, 2018. (After that date, you will still be able to view and search the forum.) Also, we're taking a second look at the best place to host future conversation. For now, keep using this forum, and stay tuned for more news.
RE: Turning off @SetViewInfo still doesn't work Andre Guirard 7.Feb.06 09:20 PM Lotus Notes Applications Development 6.5.1Windows XP
Let's consider the evidence we have...
There's not a bug report on this issue, neither referencing @SetViewInfo nor @UpdateFormulaContext, so whatever it is, is not a known problem.
I'm not certain I've ever tried this in 6.5.1, but I also haven't gotten anyone writing me back from the article I published in The View complaining that this part of the sample application didn't work. I think at least a dozen people would have tried the application, probably using a variety of versions, so there's a pretty good chance that they'd have found the problem if that application exhibited it. I haven't found that people are shy about letting me know if they encounter a problem.
This makes me think that, while the version may be implicated, there may also be something about the application. Have you tried the sample application from the View article, and does it work on your client? If one works and the other doesn't, we can look for any differences in the applications that we might currently be thinking are unimportant, but might have an effect. Is it on a server, does it open a messagebox like the sample application does, are there any documents in the filter category, etc?
Note: I'm aware that the view in the sample database works differently the first time you open it -- a different issue -- and there's an SPR for it. But it seems to work okay on subsequent uses of the view.
If you can send me a small sample application that demonstrates the problem behavior, I would be interested to test it out in different versions of Notes. Since I can debug the Notes source, doing so might help me come up with a workaround.