After deleting a break point "dot" in VBA Debugger and closing the VBA editor, and then launching "MyApplication," the VBA relaunches and goes to a location of a previous break point and stops; this happens even though the break point "dot" has been deleted. I suspect that for some reason the break point is not being iliminated, even though it is erased from the VBA editor window. How can I prevent MyApplication from going back into the VBA editor after I have finished debugging and iliminated the debugging stops? ie, there is no error because I can select "continue" under the "Run" menu and the code continues without any errors. Thanks, MikeS

This often occurs when you edit the VBA code in an open form or report (open in normal view, not in design ivew).

You can decompile the entire database by Start | Run and enter
"msaccess.exe" /decompile "PathToDatabase\DatabaseFileName.mdb"

Or you can add or delete a line of code, save the object, close database file, reopen database file, and edit the VBA code back to what it was, then compile the database.