I like this approach... but I'm assuming this prevents association of the impacted views with a template?

Interesting. One question arises here: are the bracketed dates "tdy := [06/07/2007]" actually portable across installations? In the US that is June 7th, but (albeit with periods) in Europe it would be July 6th.

Hey Sean, this is great, although it would be necessary to modify it to be date-format-neutral as JP suggests. Given that the agent is governed by the server OS date settings, the view should theoretically calculate the "correct" date as long as the db is on the server. I suspect it would break though if a local replica were pulled down to a PC with a different date format (or for that matter a server with a different format). Then there is the question of "when everyone is sleeping", which gets complicated when your enterprise spans multiple time zones.

Here's what I came up with by modifying your original agent (yes, I have tested this successfully):

********* START CODE *************

Option Public

Use "OpenLogFunctions" 'Get OpenLog from OpenNTF for those wondering

Sub Initialize

On Error Goto ErrorHandler

Dim session As New notessession

Dim db As NotesDatabase

tdystring = "ASNDtdy := "

Set db = Session.CurrentDatabase 'change this so it loops through several dbs if you want to run one agent per server

Forall v In db.Views

If Left(v.SelectionFormula,Len(tdystring)) = tdystring Then

'v.SelectionFormula = tdystring & todaydate.DateOnly &"]" & Strright(v.SelectionFormula,"]")

v.SelectionFormula = tdystring & "@Date(" & Year(Today) & "; " & Month(Today) & "; " & Day(Today) & ")" & Strright(v.SelectionFormula,")")

End If

Forall c In v.Columns

If Not (c.Formula = "") Then

If Left(c.Formula,Len(tdystring)) = tdystring Then

'c.Formula = tdystring & todaydate.DateOnly &"]" & Strright(c.Formula,"]")

c.Formula = tdystring & "@Date(" & Year(Today) & "; " & Month(Today) & "; " & Day(Today) & ")" & Strright(c.Formula,")")

End If

End If

End Forall

End Forall

Exit Sub

ErrorHandler:

Call LogError

End Sub

Using a "Today's Mail" view as a sample (new view, based on Inbox), change the selection formula to:

ASNDtdy := @Date(2007; 6; 8);

SELECT DeliveredDate = ASNDtdy

Should handle any date format, on THIS planet anyway ;-)

{ Link }

I stopped using date-based views for most applications a while ago. There are some exceptions, but really I find that .AddToFolder accomplishes what I need much more readily.

Rather than doing some kind of view with a selection formula of...

Status = "Open" & DueDate < @Today

... or something, I'll set up an agent process to gather and place all the new docs into the "Overdue" folder.

The performance advantage can be enormous, plus it allows for some fairly easy coding to move things OUT of that queue as well.

Just food for thought. As Notes developers, we're typically over-responsive to the users' request for "a view" when what they really want is "a work queue" which may or may not be best achieved through a view design element.

I use that as an advantage, Sean. Removing or adding to the folder becomes part of the overall workflow interface. :-)

It is not necessary to change this to use an OS-neutral date format. Here's why. When you save a formula, the original text of the formula is not preserved. Date/time constants are converted to an internal binary representation. Since the formula code is immediately compiled by the same system that generated the string, using "[" + x.DateOnly + "]" should work just fine -- and of course it's more efficient than having to evaluate an @Function with multiple args for every document processed.

Oh, and as for folders, that's another approach that I like. You can set the folder accesses so people can't add and remove documents manually.

Andre, nice to have you around to validate these things. So, forget everything I said :-)