I think the purpose of the trigger is to capture all non-application changes.
You can't by-pass the trigger easily, unless of course you disable it entirely. It has the advantage of being largely transparent (if written correctly, of course)...regards of where the file is accessed from. It has the advantage of having the ability to abort changes that should be done via (say) the line editor, should you code it to check and do so. With a wrap-style command, it has to be installed in all the UV accounts that you wish tracked, requiring the VOC to be updated and to remain unchanged. Of course, the wrapper is also much easier thing to install and configure, so worth considering anyway. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Webster Sent: Monday, 13 October 2008 3:51 PM To: [email protected] Subject: RE: [U2] Universe Triggers Hi Kate, As another suggestion (if only tracking changes by 'ED') why not wrap the 'ED' function and catalog it under a new name? Eg: catalog the below code as 'ED' and re-catalog 'ED' as some ambiguous name. [snipped] Regards, Dave. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
