Runtime errors Ac2007 more of same

[gg]

Is there something microsoft is not telling us about making a runtime file?
Like a lot oif people asking for help, I get constant shutdowns from runtime
errors. I have tried everything recommended on this site and others except
mztools. A consistent recommendation seems to be to put in error handling
with your code. I have, but the runtime version still shuts down on runtime
errors. Am I missing something. My error handling looks like this:

Private Sub Distance_AfterUpdate()
On Error GoTo Distance_AfterUpdate_Err

My code that works fine in regular accdb or accde

Distance_AfterUpdate_Exit:
Exit Sub

Distance_AfterUpdate_Err:
MsgBox Err.Number
Resume Distance_AfterUpdate_Exit
End Sub

Is there something else I should be doing?

 

[Tom van Stiphout]

On Sun, 6 Dec 2009 12:13:01 -0800, gg <[email protected]>
wrote:

There is nothing terribly wrong with this error handler, and it will
catch any runtime errors in the code in-between.
So if you are having crashes you may have a corrupt file (see Tony
Toews website for the corruption faq), or you may have an instable
Access installation (run Windows updates), or the error occurs in
another procedure.
You can simulate the runtime on your development machine by using
/runtime command line switch.

-Tom.
Microsoft Access MVP

 

[gg]

Thanks Tom for the quick reply. I just read about the switch. I will find
it handy as I go through the code and replace and test it, which it seems I
am going to have to do. This is very frustrating, but I guess part of the
process sometimes.