A
Alex Korchemniy
After opening, editing, and closing a vba template many times (normal
developer activites) blocks of code start disappearing and I get "phantom"
code... My team has run into bugs were the code works perfectly on the
developer machine but breaks in production and virtual machine testing. We
run into "macro security or missing code" problems, and "internal compiler
error in xxxx module". The code simply gets corrupted, sometimes works
sometimes doesn't. This problem affect any code in the template. Removing
event handlers from existing code also causes problems, somehow the event
handler is not entirely removed and some code remains. The problem can
usually be solved after rebuilding the template by copy pasting from a backup
copy saved as plain text. We encountered this problem with all version of
office currently available to the public.
What can be done to ensure that we dont run into this problem? How can we
test for this problem to make sure it doesn't exist in production code?
developer activites) blocks of code start disappearing and I get "phantom"
code... My team has run into bugs were the code works perfectly on the
developer machine but breaks in production and virtual machine testing. We
run into "macro security or missing code" problems, and "internal compiler
error in xxxx module". The code simply gets corrupted, sometimes works
sometimes doesn't. This problem affect any code in the template. Removing
event handlers from existing code also causes problems, somehow the event
handler is not entirely removed and some code remains. The problem can
usually be solved after rebuilding the template by copy pasting from a backup
copy saved as plain text. We encountered this problem with all version of
office currently available to the public.
What can be done to ensure that we dont run into this problem? How can we
test for this problem to make sure it doesn't exist in production code?