Reply to thread

Message: [QUOTE="Brian K - Project MVP, post: 4888319"] When y ou say it does not work what do you mean? What does not happen? Does anything happen? It seems like you are going a long way around. I would just have the TaskAdd event an then do the BeforeTaskChange app event and have them just write directly into the field for a change or addition. you are using the ProjChange event which does not give you any view into which task changed. the before task change event works just like the TaskAdd event but gives you a hook to the task that changed, the field that changed and the old and new values. So with that you could have the Text5 field (by the way trap a change to the Text5 field to ensure that the code in the event does not start a never ending loop LOL) read what field changed. This would let you get rid of all that code that is trying to capture IDs of new tasks and such. Have the TaskAdd event get the new ID and just insert ADDED into the Text 5 field right there in the event rather than setting a boolean flag and then having the change event write it. I hope this helps. [/QUOTE]