When working on developing or debugging an app created by automation (for example, by ActiveX DLL), if you normally invoke that app from a calling program (EXE), leave the calling program running and run the app you’re debugging in the VB Integrated Development Environment (IDE)-gotcha! Your debug and breakpoints won’t get hit. The calling program still has the “real” automation project in memory and isn’t using the version from the VB IDE. You must close down the calling program that’s running and restart it to use your VB IDE version. You’ll see an example of this when you try to make your automation project into a DLL and it balks, saying “Permission Denied.” You need to close down any calling programs.