Is there such thing as updating view index via background? I have created few view, but everytime it will require some updating before it is being updated, my data is only being updated on early or later of the month. sometime, I just need the view to be displayed without having any new document to be updated.
I tried automatic, but I am bit puzzle why the view still needs to be updated when I opened the database when no new documents required?
Subject: What view setting will make view display fastest?
You’d need to give more details about the view selection criteria (selection formula) and any column formulas you have for anyone to give you a solid answer.
That said, I suspect you are doing something with dates or time in your view.
Subject: RE: What view setting will make view display fastest?
My view selection is simple, just select document that uses formA, but my view column formula is complex, with checking against @Now. The problem is that I sometime adds data, so if I select refresh manually, I will need to go to designer, change it to automatic, and open back the database, otherwise, by pressing F9, it will lock my notes client. Thus, I thought automatic will make the view index update on the background, but this does not happen, I always get the message that view is being updated, although no new documents created. Thus, appreciate your guidance.
Subject: RE: What view setting will make view display fastest?
Tq Raphael, for your suggestion, sorry if this question is bit silly, where can I find the link for Developer Network on this matter? Again, thanks in advance.
Subject: What view setting will make view display fastest?
Using @Now in a Selection Formula or in a column formula is a quick way to kill an application. There are some ways to get around this, none are perfect. A number of years ago I built an application that displayed a little thermometer in a view based on the age of the document. This worked 100% in the development environment but died a very nasty death as soon as I moved it to the production environment. What I ended up doing is creating a field in the document that I updated early every morning (1 - 2 AM) via a scheduled agent. Then using the value in that field displayed the correct ICON and was also used in the selection formula. Because the value in the field was static the views functioned well. The down side is that if the Database is replicated you might be replicating a lot of documents, but since it was run early in the morning the replication is all out of the way before the DB got busy.