Forum Discussion

  • John-project's avatar
    John-project
    Silver Contributor
    Jamesp435,
    Paul provided an excellent reference, let me add a word of caution. The Change Event has been available since the early days of Project VBA but it must be used with care. Since the event is fired for every change, (with the exceptions noted in the article Paul referenced), the macro can slow things down considerably. If you want to limit the "slowdown" overhead I suggest you include a test at the beginning of the macro code that "bails out" if the change is not related to the field of interest.
    John
    • Jamesp435's avatar
      Jamesp435
      Brass Contributor
      That's a good point John. That's what I did when doing a lot of Visio VBA a while back... Cheers

Resources