Re: Obtaining the complete code for a trigger from systrigbody

> > If you are trying to get the SQL for the current triggers, try running > > "dbschema -d database -t table". Or is there some reason that you need > > to go through the catalog tables? > > > > I need to go to system catalog because I want to include my own trigger > with the existing one of the table, and the existing triggers can be > modified by the software house who has developed them. Yes, I understood that. I just don't understand how querying the catalog addresses this problem better than using dbschema. How often do you expect to run your catalog query? Will your program then automatically alter (drop/create) the trigger to add your new trigger logic? Given that a third party can make changes to the triggers, can you reliably automate the addition of new logic? It still seems to me that you could just as easily capture the output of dbschema and programatically parse it or manually edit it, then run it through dbaccess. Mark Collins mcollins@us.dhl.com Windows 95: 32 bit extensions and a graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit processor, written by a 2 bit company that can't stand 1 bit of competition.