3043 Disk or network error.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • munkee
    Contributor
    • Feb 2010
    • 374

    3043 Disk or network error.

    All,

    I know the reasons for the error: 3043 Disk or network error.

    However my question is when one of these errors occurs access becomes totally unusable, as in it requires the task manager to close it otherwise the error box just keeps flashing up.

    Is there a more neat way to trap this error and just exi the database and re open it for instance?

    Thanks,

    Chris
  • Adam Tippelt
    New Member
    • Nov 2010
    • 137

    #2
    When you say it becomes unusable do you mean it keeps throwing up the error even when you tell it to end?

    Ctrl+Break will sometimes stop an error from looping round.

    If you're using adequate error trapping that throws it up in a message box instead of opening the VB Editor window, you could try adding a clause in to handle specific error codes:


    Code:
    Private Sub YourProcedure()
    On Error GoTo YourProcedure_Err
    
    <YOUR CODE HERE>
    
    YourProcedure_Exit:
        Exit Sub
    
    YourProcedure_Err:
        If Err.Number = 3043 Then
            Err.Clear
        Else
            'Do you normal error trapping.
        End If
        Resume YourProcedure_Exit
    By the way this will only work if you have your code set to only Break on Unhandled Errors - you can check this by looking in the VBA Editor under Tools -> Options -> General Tab - > Error Trapping.
    Last edited by Adam Tippelt; Jun 24 '11, 04:13 PM. Reason: Made the code sample clearer.

    Comment

    • NeoPa
      Recognized Expert Moderator MVP
      • Oct 2006
      • 32633

      #3
      If you know why it happens Chris I would do all you can to ensure it doesn't.

      Due to the nature of the problem this is often followed by corrupted and unreliable data and may cause the database to become unusable.

      Comment

      Working...