It is highly likely that from the navigation lists the code does not run that your custom VBA change triggers from. Turn on Debugging in the Dex.ini and capture a script (Debug > Log Scripts) when it works in the window and capture another script when processed from the nav list. Comparing them will likely show a different logic path in each. You will probably need to write a Dexterity customization containing a trigger on a procedure you identify in the nav list logic path. In case you are thinking of a database trigger, I would recommend against it in this situation. You would not wish to update the Doc Date on every update to the table record, and a database trigger will lack the situational awareness that triggering on a specific procedure will.
↧