Please pardon my misstatement as you can put one update and one delete (for a total of two) triggers on a UniData file (there is a work-around). You can, however, debug the trigger by putting a DEBUG statement into the subroutine.
Bill > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett > Sent: Thursday, April 20, 2006 7:55 AM > To: 'U2Users' > Subject: RE: [U2] [UV] Triggers > > Phil: > > Fortunately, this is not the case in UniData. However, > triggers (plural) is > really a misnomer as you can only put one trigger (singular) > on a UniData > file. > > Bill Haskett > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of phil walker > > Sent: Wednesday, April 19, 2006 11:02 PM > > To: U2Users > > Subject: [U2] [UV] Triggers > > > > How many people in this group as using triggers in there > applications? > > > > For those that do, how do they manage to use the debugger? > > > > As from what I have been able to ascertains it seems as soon > > as you try > > to debug a program which write/deletes to/from a file/table with a > > trigger on the program aborts, as you cannot have input within a > > trigger. > > > > This is a major design flaw as far as I am concerned, and very > > frustrating... > > > > Firstly, if someone wants to have an input statement inside > a trigger > > program let them. There is enough rope in UV for people to hang > > themselves. So let people make their own bed... > > > > Secondly, even if you cannot have input inside a trigger, > the debuging > > session should not be considered normal input, and UV > should recognise > > this and perform the write, stepping over the trigger code and > > performing the next operation in the program being debugged. > > > > Any comments? > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
