Re: Trigger programme without a trigger.

[CRPence <CRPbottle@xxxxxxxxx>]

  That expense for an I/O trigger is why I had suggested in my first 
message, that a request for design change is probably a good idea, to 
ask for an /open trigger/ for a file.  But I had also alluded that the 
database open exit could suffice in place of that non-existent function.

  I did not note however, my concerns with that exit point; i.e. for 
why I suggested an open trigger would be better.  Both rename and move 
of the file would make knowing which file is being protected, more 
complicated [or at least less intuitive], for the program invoked by the 
open exit.  Plus the database open exit is for [effectively] all opens 
rather than specific to a file.  It could be assumed that the rename and 
move would not be an issue when using the open exit, and that an open 
trigger would be expected to remain with the file.

Regards, Chuck

Joe Pluta wrote:
> <<SNIP>>
> I actually kind of like Rob's idea of checking the stack and sending
> a message, if it weren't so expensive.  <<SNIP>>