Runtime error not functioning A2007

[gg80]

My runtime error code doesn't "run" in A2007. The program acts as if there were no OnError goto etc. Here is an example. When I run this, I get the pop up announcing run-time error 2002 . I was told that removing Option Explicit from the declarations section would fix this, but not so. Using W7 on 64 bit computer.



Private Sub import_Click()
On Error GoTo Errx
DoCmd.RunCommand acCmdImport 'In A2007 , will generate err 2002
call GoImport
Exit Sub

Errx:
If err.Number = 2002 Then 'means using Acess 2007, need different command
DoCmd.RunCommand acCmdImportAttachAccess
call GoImport
End If

End Sub

[RuralGuy]

You have no action if it is an error other than 2002. It just exits the sub. At least show a MsgBox with the error. Have you single stepped to see if it is throwing an error?

[gg80]

You have no action if it is an error other than 2002. It just exits the sub. At least show a MsgBox with the error. Have you single stepped to see if it is throwing an error?

Hi and Thanks for quick reply. I did single step and only gets to the first import expression, then pops up with the very run-time error message that (2002) that I am trying to trap. I have tried the repair utility to no avail. any ideas?

[RuralGuy]

I just tried your code in a 2007 accdb and it worked just fine. Single stepping, it took the OnErr trap. Is your system fully patched? Both ac2007 and the OS!

[gg80]

I get all the updates regularly, but did it again to make sure, both for Office and W7. I also ran the repair utility, then uninstalled and reinstalled Office 2007 and downloaded service pak 2. Still no good. It isn't just for this code, but for all my code. It just won't recognize onError. Ever hear of it before or know where I might go to find something out? Runs ok on my wife's machine with w7 and A2003

[RuralGuy]

When you open a module with code and go to Tools>Options>General tab - how to you have error trapping set?

[gg80]

Hi-and thanks again. It is set for "break on all errors" I tested it on a simple form with one button coded to open a non-existent form. When I changed it to "break in class module", it trapped the error. When I leave it on "break all errors", it doesn't trap. I must not know what "break" means. Intuitively, it would seem that Break on All is what I would want. Do I change it to the class option and how would I make it the default mode if so.?

[RuralGuy]

I leave mine at "Break on Unhandled Errors".

[gg80]

Thanks so much. If you are ever in the SF Bay Area, I owe you at least the first 3 rounds. This was driving me crazy. Your willingness to stay with it to the end is much appreciated.

[RuralGuy]

I used to live in Hayward, Belmond and Redwood City. Have fun.

[RuralGuy]

BTW, are you ready to follow the link in my sig and mark this thread as Solved?

[RuralGuy]

BTW, are you ready to follow the link in my sig and mark this thread as Solved?

Nevermind. I see you got it. Thanks.