<quote who='Israel, John R.' date='Monday 29 December 2008'> > Put a DELETE trigger on the VOC file and in the code, specifically test for > just the VOC item that keeps getting deleted (i.e. ignore any others). > When you get a hit, immediately send your self an E-mail with all the info > in question. > > Remember that triggers must be globally cataloged, but that they can call > locally cataloged programs (thus you can have differences between accounts > by having the subsequent subroutines different between accounts). > > I hope this helps.
I was thinking the same thing, but this doesn't address the issue if there's an O/S process that's deleting the VOC outside of uv. If the process deleting your VOC is outside of uv, it may be harder to identify. -- Jeff Butera, Ph.D. Administrative Systems Hampshire College [email protected] 413-559-5556 "Where I'm from, we believe all sorts of things that aren't true. We call it 'history'." The Wizard, Wicked ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
