Automated way to "Clear All BreakPoints"?

[TomCarnahan]

I am writing a utility to do some of the cleanup necessary for deploying our MS-Access applications in a standard orderly fashion.

I have figured out how to disable the shift key, turn off builtin menus, hide the database window, and a few others. The only thing that I am having trouble with is using VBA to clear all breakpoints in the VBE.

I know that there is: DoCmd.RunCommand acCmdClearAllBreaks

I am assuming that this is the VBA equivalent of going to the menu and selecting "clear all breakpoints" however, when I use it, I get a message that "this command is not available at this time."

Is there something I am not aware of? Is there another way to do this?

Thanks ahead of time for any help you can provide!


--- Tom

 

[Remou]

According to Microsoft, breakpoints are not saved, so won't the decompile and recompile cover any possibility that one might get stuck?

 

[TomCarnahan]

Remou,

I am not so sure about that. I have saved .MDB files with breakpoints in the code. When I reopened them, they broke where the breakpoints were ... even though I could not see them. Go figure! I haven't figured out why, but I don't take chances anymore.

Being able to use automation to clear them is one of a number of steps in a sequence that is easy to mix up. I am trying to have a one-click "lock-down" on code that is going to the customer. By the way, it this case, I do not have the option of compiling or using .MDE files, so the best I can do is to disable built-in menus, hide the db window, disable builtin menus, etc. It all has to be done in sequence or it does not work. Automation would ensure consistency and allow me to be able to get it ready for Production a lot faster and accurately.

Would you know anything behind why some DoCmd.RunCommand items work with automation and others do not (i.e. report they are "not available at this time"?)


--- Tom

 

[Remou]

I am aware that breakpoints occasionally get stuck. The decompile I was refering to is the decompile switch:

http://www.granite.ab.ca/access/decompile.htm

It is probably an important step in preparing your DB for production.

By 'Re-compile', I mean the normal Compile, from the code window menubar.

The usual reason DoCmd.RunCommand is not available, is that what ever it works on is not available or has not got focus. For example, you cannot Freeze Columns without coulmns to freeze.