Re: Trigger programme without a trigger.

["Bob P. Roche" <BRoche@xxxxxxxxxxxxxxxxx>]

> > As for firing off during development. We only keep triggers in our test 
libraries if we are testing and need the trigger as part of your test.
> > Triggers are live on production files and we don't develop over 
production data.

> How do you go from live to notlive?


We have 2 separate library lists. The last company I worked for had a 
development system, developers only. One library list contains the 
production libraries, the other contains only test libraries. The files 
are all the same, unless test has a newer version we are working on. A 
change management system handles moving the object around from my 
development library, to test and then to production. The users only see 
production libraries. So if we have a problem testing a program its only 
test data that needs to be reset.