Results 1 to 2 of 2
  1. #1
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,015
    Thanks
    0
    Thanked 3 Times in 3 Posts

    No Visual Basic Error Trapping (Access XP)

    I am running Access XP on Windows XP Pro SP1
    For some reason Error trapping no longer works in any Office VBA Application
    If an On Error Trap is placed in any VBA code in any of the windows applications it does not work.
    However, VBA and the programs work fine apart from this.

    Anyone know how to fix this problem, or have seen it?

    I have tried to repair office, but it makes NO difference
    I have completely un-installed Office, but it makes NO difference.

    Suggestions would be good, because it is wrecking my development error testing.
    It also means I cannot run apps on this pc because errors are not handled.

    Interestingly , if a VB6 Application is run, the error trapping works just fine
    but not in XP.
    Andrew

  2. Subscribe to our Windows Secrets Newsletter - It's Free!

    Get our unique weekly Newsletter with tips and techniques, how to's and critical updates on Windows 7, Windows 8, Windows XP, Firefox, Internet Explorer, Google, etc. Join our 480,000 subscribers!

    Excel 2013: The Missing Manual

    + Get this BONUS — free!

    Get the most of Excel! Learn about new features, basics of creating a new spreadsheet and using the infamous Ribbon in the first chapter of Excel 2013: The Missing Manual - Subscribe and download Chapter 1 for free!

  3. #2
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,015
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Re: No Visual Basic Error Trapping (Access XP)-OK

    Forget it folks.
    I've had a long week and my brain was in melt down.
    I had accidentally set the flag in the Editor options to
    Break On all errors not Break on un-handled errors

    Then to compound my stupidity
    I ran a test routine in Excel that tried to raise the error with a NON-EXISTENT error number.
    Now how stupid was that.

    Sorry folks !
    Andrew

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •