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 February 2024SQL Query on Matomo Database to Calculate the Number of Visits to Each Page
- Dyn365GP2 February 2024New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Use Virtual Tables to Expose More Business Central Data in Dataverse
- Dyn365GP2 February 2024New Functionality In Microsoft Dynamics 365 Business Central 2024 Wave 1: Manage Work Orders in Field Service, Invoice Them in Business Central
- Dyn365GP2 February 2024In Microsoft Dynamics 365 Business Central (Inventory and Warehouse Management), how do I… Manage Consignment Stock at a Customer Location