Why does it take VBA onaction syntax to resolve error for inelegant powerdown?

[Ken Macdonald]

In the 2007 help files examples provided for onaction syntax look like
.onaction = "DoAction"

Recently my computer powered down inelegantly - no other damage except that a macro in the personal file containing an 'onaction' statement failed on that line and even closed that file down. If you manually opened the file then debug launched at the problem line.

So decided to re-install Office which subsequently did but to little avail. Then searched the web for 'vba onaction fault' topics and came across pages that suggested that you could call functions and pass parameters ie
.onaction = "=DoAction()"

By calling the procedure as a function I have now resolved the problem but my question is still WHY?

Thanks for any suggestions

Ken

[TheSmileyCoder]

Try doing a decompile.

You this by going to Start->RUN and typing:

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" /decompile

I think that for AC2007 you need to use OFFICE12 instead.

Now open your database while holding down SHIFT. Then open VBA editor window (ALT-F11) and press DEBUG->COMPILE.

[Ken Macdonald]

Thanks SmileyOne

I neglected to say I am actually using VBA in excel but I reckon I would get the desired result if I substitute MSEXCEL for MSACCESS

[TheSmileyCoder]

To be honest I don't really know. Access will allow code to be compiled when needed, and even at runtime, when you are in debug mode, you can change code (I STRONGLY ADVICE AGAINST IT!!!.) and access will do a partial compile.

While this can seem extremely handy, I have also on more then 1 occasion seen it cause corruption in access.

Therefore, when I get my error msg (Which of course NEVER happens :) ) I click the debug, to see the highlighted line, and then kill the process from the VBA window. Then I change my code, click Debug->compile, and try again. Changing code on the run is a great way to corrupt access, in my oppinion.

Now that was alot of ramble about access for an excel question. I really have no idea about whether excel does partial compiles as well, but I would imagine it to be so. Doing a decompile (and subsequent compile) can solve some of these problems, and have saved my *** once or twice.