in livelink usually the dataid after it is introduced is the create date.If the date is indeed changed by a event that is audited that is what
I think Greg was trying to tell you.If the event is not auditable you cannot know that.If it really needs to be a witch hunt then unless the
user attacked the database directly you can pretty much find the information from webserver logs(I used LogParser from Microsoft to find playing people)
and we use SummaryTimingsLogs so it records everything with a userid context.
Now some of the things that change the ModifyDate is hard for a lay person to understand.
If you are on the side of the people that stands ModifyDate of a Object is sacred,then anything on that object say addition to ACL's(permissions),metadata changes etc changes it
It follows the file system paradigm.
However if you are on the side of the people saying that modifydate should not change unless a person changed name or content then that is also true.
Ot has built flags so that both sides can be kept happy.
If it is indeed a person who hanged something then the performerid that you see in DAUDITNEW is the KUAF.ID of the user a simple join or
using the administration gui for audit events can give you the real name of the user,if it was audited .
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010
