A client reported a problem with some VBA customisations in Microsoft Dynamics GP where the code was stopping as if at a debug point in two places even thought there were no debug points present. Once a user hit F5 to continue the code past a “debug” point, they would not see the problem again until the next time they logged in.
I did a lot of investigation and fiddling around, but could not…
Continue Reading azurecurve’s Article on their blog
Microsoft Dynamics GP VBA Entering Debug Mode Without Breakpoint For All Users On First Login
A client reported a problem with some VBA customisations in Microsoft Dynamics GP where the code was stopping as if at a debug point in two places even thought there were no debug points present. Once a user hit F5 to continue the code past a “debug” point, they would not see the problem again until the next time they logged in.
Blog Syndicated with azurecurve’s Permission
More About This Author
Array
- Dyn365GP3 May 2024New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: See Improved Usability for Warehouse and Inventory
- Dyn365GP3 May 2024New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Automate the Reminders Process in Collections
- Dyn365GP2 May 2024New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Allow Lines with Amounts of Zero on Recurring General Journals
- Dyn365GP2 May 2024New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Specify Dimensions on Posted Entries Applications With Realized Gains or Losses