Tracking which user created a view

[imanminhas]

Some of my processes have stopped working - looking at the message log, it seems that someone has created a view using a subset, that my process uses. Message log says "zTempMonthSubset" is being used by a view and cannot be deleted" (the subset is a balance b/f)
Can anybody please help me to track down who created this view and how I can get rid of it??
Many Thanks,
Iman

[Steve Vincent]

if you have a program that can search for text in files, the easiest way is to search all .vue files in your data directory for the name of the subset. i have a program that can do that but for various reasons i'm not able to share. as long as the output includes the filepath, that will then tell you the user ID of who has used the subset.

[Steve Rowe]

Also note that the server is not 100% reliable in this area. It's quite possible to have this error when you build and delete the view and subset within the TI process. It's worth checking is you cen delete the subset manually through the server explorer before you go hunting for a view.
Cheers

[Alan Kirk]

Also note that the server is not 100% reliable in this area. It's quite possible to have this error when you build and delete the view and subset within the TI process. It's worth checking is you cen delete the subset manually through the server explorer before you go hunting for a view.

I'd add to that; there are occasions when you yourself may get a lock on a subset, usually if you've examined the view at some point. The server will sometimes incorrectly report that the subset can't be deleted but in reality all you need to do is restart your client session (as in, bounce Excel completely) and you can then delete it.

To get around this issue we always assign a unique name to subsets which are built using a TI; our chore control cube includes a cell indicating how many times a chore has been run and increments it with each run. The subsets are then named BaseName_1, BaseName_2 etc. which ensures that we never have a problem with them being locked and interfering with a future run of the chore.