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
- Dyn365GP23 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Delete a Company
- Dyn365GP22 April 2024Upcoming Microsoft Dynamics 365 Business Central Knowledge Hub Webinars (May-Jul 2024) from MADIC dynamics
- Dyn365GP22 April 2024In Microsoft Dynamics 365 Business Central (Administration), how do I… Rename an Environment
- Dyn365GP19 April 2024MADIC dynamics Knowledge Hub Webinars: Jet Reports & Business Central