You are correct. The trigger definition (call some program after insert)
is part of the file description, but the program performing the action
is its own entity.
You can restore the data file and trigger program separately, with no
ill effect. The only time there is an issue is when the trigger fires,
then it must find the associated program. ADDPFTRG allows a program
library to be named, providing the separation of data and programs. What
I want to know is, what does the trigger library (TRGLIB) parameter do?
The help didn't.
We do like you, storing data separate from the objects acting on the
data, including trigger programs. Both are owned by the same profile,
and both libraries (data and programs) are in the application's master
library list.
Loyd Goodbar
Senior programmer/analyst
BorgWarner
TS Water Valley
662-473-5713
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian
Sent: Wednesday, April 04, 2007 12:59
To: Midrange Systems Technical Discussion
Subject: Re: Adopted authority and triggers
Hmm, I never have thought of a trigger program as part of the database.
It
is linked to the database but is it really a part of it?
midrange.com
