You could possibly create a VB macro to do something like that but IMHO it
would be far more trouble than it would be worth to do it. A project plan
should not be such an automated rote exercise anyway. You, the manager,
still should be in charge of all the decisions as your plan goes from rough
draft to final work schedule. MSP is just there as a glorified calculator
to help you see the consequences of the choices you make but they always
need to remain YOUR choices as only you know what meets the required
objectives in the end. In the case of lag time, even if a certain pair of
tasks occurs repeatedly in your plan, for each iteration of A->B you should
be looking at it and asking yourself "Based on the conditions at the time we
doing them, what should the lag time between A and B be *this* time around?"
In most projects I would think it would rarely be the same for all
iterations of the tasks.