How to fix Runtime Error 6 overflow

Written by susan reynolds | 13/05/2017
How to fix Runtime Error 6 overflow
Runtime files help the program run faster. (keyboard - error image by Kirubeshwaran from

The Runtime Error 6 occurs in the Visual Basic programme. It is an overflow issue that can occur when the Visual Basic programme attempts to store too much data in the temporary folders area. Runtime files help Windows translate a programme's language into Windows language so the programme runs faster. You can get the Runtime Error 6 message for several reasons. One reason is that you are using a backslash instead of a forward slash in one of your calculations. Other reasons include an overloaded temporary folder, outdated software or a registry error.

Fix registry and clean temp folders

Download and install a registry cleaner programme onto your computer (see Resources). This software will automatically empty out temp folders and fix registry errors that cause programmes to malfunction.

Close your browser windows and any other running programme.

Open the registry cleaner programme and direct it to scan and fix your registry and clean out old folders. Wait for the programme to scan your computer for errors and empty out old files.

Restart your computer.

Update Visual Basic software

Go to the Visual Basic Updates page (see Resources). This is where you can download and install new Visual Basic runtime files to fix the overflow problem.

Click on "Download" and save the file to a location on your computer. Wait for it to download.

Double-click on the file to install it automatically. Restart your computer when the installation is complete.


Check your Visual Basic calculations to make sure they fit within the range of the value.

Things you need

  • Registry cleaner

Show MoreHide

  • All types
  • Articles
  • Slideshows
  • Videos
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the site, you consent to the use of cookies. For more information, please see our Cookie policy.