Is there another function in 6.5 other than @Now which will allow me to use for view selection formula and doesn’t hit performance.
I know there are other solutions like having a field which can be set a value of @Now by running a daily scheduled agent for all documents in the database and use that field instead of @Now in the view selection. I don’t want to use this solution just because I want real time (@Now)
Subject: Is there another function in 6.5 other than @Now to use for view selection formula which doesn’t hit performance
No.
Subject: how about @TextToTime(“Today”)
there are some drawbacks so do a search in this forum on that solution.
Subject: Is there another function in 6.5 other than @Now to use for view selection formula which doesn’t hit performance
As already suggested you can do an @TextToTime(“Today”) the problem is that tomorrow the view will be out of date. We had an application where we wanted to change an icon in a view based on the number of days it had been in the view. During design the @Today worked great and only became a problem a few weeks after the roll out (bummer). What we ended up doing is using the @TextToTime and had an agent that ran once a day that rebuilt the index and that turned a really slow application into one that ran very nicely. At the time that we did this you could not set the time that an agent should run at as finely as you can now. So you should be able to set it to run at 12:05 Am or something like that. The downside is that the agent may modify a lot of documents and if the DB is replicated there could be a lot of activity.
Another issue would be if you have an agent that runs on New or Modified Documents you may need to modify it to ignore these changes. Personally I’ve been badly burned by agents running on New or Modified documents. I prefer to add a flag that identifies new and specific modified documents and then have a scheduled agent that picks off the flagged items - but I digress.
Subject: RE: Is there another function in 6.5 other than @Now to use for view selection formula which doesn’t hit performance
Andre Guirard suggested a couple of years back that a reasonable way to do this in ND6+ would be to hard-code a date into the view, then use the new NotesView methods to programmatically change the selection formula every night rather then touch the documents. That would leave the “new and modified” properties alone, if that’s of any help. You’d have to be mindful of when (or if) Design runs on the database – although it’s more or less a “special case” of replication, I’m not certain that it obeys the last modified flag.
Oh – to the original poster: this is still a once-a-day change, not “real time”, so if you need (or think you need) on-the-fly, real-time changes in indexing, you’re still out of luck.
Subject: Is there another function in 6.5 other than @Now to use for view selection formula which doesn’t hit performance
Hard code a date into the selection formula; change it once a day with a Lotusscript agent (notesview.selectionformula = “[blah blah blah]”). Bear in mind that the results might not make sense for someone on the other side of the date line.