RE: trigger program: can I fool a program into reading some selec t fields from another file?

Excellent rick.  And he can lock down maintenance at the divisions with 
update triggers.  The trigger will have to allow the updates if the job is 
from Central.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




rick.baird@xxxxxxxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
10/13/2003 05:04 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: trigger program: can I fool a program into reading some selec       t 
fields from another file?






Joel,

it appears that you will not be able to adhear to your #1 rule of database 

design.  the design is already done.

my advice would be to update all descriptive data in all of your satellite 

item files to match the corporate master, and implement an 'after/update' 
trigger on the corporate master. 

In your trigger, if any of the before and after buffers for the 
descriptive fields are different, update your satellite files for that 
item with the new item.

for one thing, you aren't running a trigger on EVERY SINGLE READ ;) of the 

various satellite files, you're just running one when the corporate record 

is changed, and then only if they change the descriptions.   that's going 
to save you a lot of cycles.

I would then lock down maintenance of these fields at the satellite level, 

because any work done there would be superflous, unproductive and probably 

downright frustrating for anyone trying to change the fields :)

hth,

Rick Baird
317-655-7318
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.