I have an application that has grown [how strange] and now has approx 80 users.When there were 2 (as per the original design) the readers fields imposed no noticable performance problem.
Now, the opening of views is (understandably) slow.
This is a Notes app, not a web app. On the web I can design a view categorised by the user’s name, and pass a parameter to the URL to restrict the view just to the user’s name. This way, I could get rid of the reader fields (assuming security is not a concern!).
How can I do the same thing in a Notes App that uses an outline for navigation?
I’ve considered using a form with embedded views, but it means re-writing all the navigation. Any other ideas?
Subject: slow performance due to reader fields
if the readers fields are not really used for security purposes then just get rid of them altogether (or change them to names fields instead), categorise them as you were going to and use like that.
if security is an issue then you don’t really have much choice but to leave them there.
Subject: RE: slow performance due to reader fields
hisee this help
Minimize the Use of Reader Name Fields When Possible
Using reader name fields on many or all documents in a database with a lot of documents can significantly affect view performance, because the database has to evaluate the reader fields on a number of documents before it can even display a view. There’s a good article on the problem and possible solutions on the LDD site.
In short, you should Categorize all your views if you’re using Reader fields extensively on a database with many documents (and make sure that “Collapse all when database is first opened” is checked, as it always should be). In ND6, I think you also need to have the “Don’t Show Empty Categories” option turned off for this to be effective.
In R5 and higher, you can also use “single category” displays of the view on a Page or Form to help even further. In ND6 and higher, you can use the @SetViewInfo command to dynamically filter a view.