View to display documents by the current user.

reference answer: https://www.experts-exchange.com/questions/20568247/Viewing-documents-where-the-current-user-equals-the-user-name-in-a-specified-field.html?query=lotus+view+current+user&clearTAFilter=true

I have been trying to create a view to show the documents created by the current user accessing the view. I thought I found it in the question referenced above.

Here are the details:

1. I created a view with the View Type option set to "Shared, Private on first use."
2. The selection criteria is set to: SELECT (@Name([CN]; Author) = @Name([CN];@UserName))

It appeared to work fine, but I have a couple of reservations.

This is what is in help on "Shared, Private on first use.":

****
Shared, private-on-first-use views
A "Shared, private-on-first-use" view begins as a shared view and becomes a private view as soon as a user accesses and saves the view. These views give you a convenient way to distribute personal views to multiple users. You usually create this type of view by using @UserName to customize the display for each user.
Note that this is the only way to make a view work with @username, because the view selection is only parsed when the view is generated. Thus, if Tom opened a shared view that keyed to @username, all of Tom's documents would display. But, if the view is still open when Jay accesses it, Jay sees all of Tom's documents, and does not see his own. So, to avoid this conflict, designate the view as "Shared, private on first use" when using @username in the selection formula.
After a user saves a shared-to-private view, the user's copy of the view no longer inherits design changes. For example, if you add a column to the view, anyone using a private version of the view won't see the new column. To obtain design changes, users must delete their private versions of the view and open the shared-to-private view again.
Shared-to-private views are not a security measure, as they do not protect data. If you create a shared-to-private view that omits certain documents, a user can still create a private view that includes them.
Shared-to-private views are stored in the database as long as they are shared. After the first use, Domino uses the "Create personal folders/views" option to determine where to store the view.

***

As it says above, a new view and view index are created for each user, however, the problem is that the new views are set to not refresh and from what I can see, the design and data is only viewable by the user they are created for. As a Manager, I cannot go and force a new design down, I cannot flush views so they can be recreated, I cannot clean them up, I cannot set them to refresh design, since I cannot even se them, etc. etc.

The only work around that I see is that if I made a design change to the view, I would have to rename it, update all code that pointed to it, people accessing it would create all new private views the next time the accessed the view, but the old views would still be setting out there taking up space. The only way I know of to remove an old personal view would be to have the person it was created for to go in and delete it. Not exactly an efficient answer.

Anyway, if any of you very bright people out there has an answer to this, I would appreciate it.