Modify, Insert, etc ... parameter

Maybe this is a very silly question, actually more a helpless complaint than a question - but why in the world is the Run Trigger parameter in MODIFY, INSERT and DELETE functions set on FALSE by default? What’s the use to put code on table triggers, if you still have to retrieve and change code everywhere else? SIGH! --------------------------------- moved Edited by - rmotzer on 2001 Jul 09 10:08:52

I find that it really isn’t much of an issue for me. As often as not, I do NOT call the trigger code. When I don’t call it, it is usually a batch job or some type of correction. Also, in posting routines (where modify, delete, and insert are used most often) you rarely call the trigger. CU 80 & 90 come to mind as examples. Would it hurt to default the other way? Probably not. However, I have tried to start always putting in the parameter even if the default is the value I want. That way, it’s easy to tell what is going on even if you don’t know the default value. Which brings me to another point. Although it is not standard Navision to include the () when calling a function without parameters, I always do so that it is obvious that it is a function call and not a variable. What do you all think? Bill Benefiel Manager of Information Systems Overhead Door Company (317) 842-7444 ext 117


Originally posted by Anna Perotti: What’s the use to put code on table triggers, if you still have to retrieve and change code everywhere else? SIGH! ---------

It is very important to put table triggers for the integrity and security of data. There are some advantages of using table triggers. Some times we required to add/modify data to the same table from different screens. If we code the validation in the table trigger ,it will avoid coding the same thing in different places. It also validate data if someone change the data directly through backend. But some table triggers will activate only we do modifications through forms or direct in tables. eg. validate trigger. We have to use ‘Validate’ function to activate validate trigger in batch jobs. This disability of validate trigger is very help full when we import some data through dataport. Recently we had to restore some old datas to the system for some analysis. But unfortunly some datas were not keeping the relations to other tables. The table’s validation triggers are not allowed to enter these details directly. So we opted the dataport for this Job. Regards Joseph Mathew