Runtime Error '52' Bad File Name or Number

Runtime Error '52' Bad File Name or Number

PROBLEM

  • When opening Gorilla, you get Run-time error '52': Bad file name or number

CAUSE

The path you are trying to open is not accessible.

SOLUTION

Check to make sure that you are connected to the network. To do so:

  1. Click Start>My Computer.
    • For Windows 10, right-click Start>File Explorer
  2. Double click on the network drive where Gorilla is located. If you are not sure where that is, check to see if anyone in your office knows. If no one does, contact your local IT dept.
  3. If it does not open, your network connection is off and you must contact your local IT dept.
  4. Go to the Gorilla database file (B43.mdb) and try to copy and paste it to your desktop and back.
    • Note: The file name may be different depending on your version of Gorilla.
  5. If it does not let you paste it back in you do not have permissions and must contact your local IT dept


In rare cases your mapped network drive might have been changed and you need to reset the Gorilla directories. Please contact Software Support at 801-553-9888 for help in getting this done.  


​

    • Related Articles

    • Runtime Error '429'

      PROBLEM “When I try to open or close Gorilla, I get a runtime error 429. How do I fix this?” “Why do I get an error 429 when I try to edit or create a document?” CAUSE The problem happens because of an error in the system configuration, or a missing ...

    • Runtime Error 76, Path not found in Gorilla 4.x

      QUESTIONS THAT APPLY TO THIS TOPIC “How do I fix an Error #76 when I try to import a satellite?” “How to I repair a ‘path not found’ error with my satellite?” ANSWERWhen trying to import to a satellite installation of Gorilla, an error stating ...

    • Automation Error or Runtime Error 3251

      PROBLEM Automation Error or Runtime Error 3251. CAUSE The “automation error” and the “runtime error 3251” both refer to the same problem: A corrupt installation of Microsoft Office or one or more of its components. SOLUTION To remedy this problem, ...

    • How to Fix Runtime Error 339

      PROBLEM Run-time error '339': Component 'MSCOMSTL.OCX' or one of its dependencies is not correctly registered: a file is missing or invalid. Run-time error '339': Component 'COMDLG32.OCX' or one of its dependencies is not correctly registered: a file ...

    • Word could not create the work file

      PROBLEM When saving a document in Microsoft Word, you receive the following error message: “Word could not create the work file. Check the Temp environment variable.” CAUSE The Temporary Internet Files folder for Windows Internet Explorer is set to a ...