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 work out what the issue was.
Eventually, I used Customisation Maintenance to export the two problematic packages and then imported them again. When we tested, the problem had gone away.
I do not know what caused the problem, but it looks like even though there were no visible debug points there was something in the two files making Dynamics GP appear as if there was.
I’d be interested in hearing from anyone who has encountered this issue before and might be able to explain what was happening.
We have a project on the go to replace the VBA modifications, which are quite complex, so for this client the should only be a short term possibly of it reoccurring.
What should we write about next?
If there is a topic which fits the typical ones of this site, which you would like to see me write about, please use the form, below, to submit your idea.