Runtime Error

A RUNTIME ERROR generally means that something is running in the background or a file is in use.
RUNTIME ERROR 7:Out of Memory errors are common in Windows environments even when a system has a large amount of memory. Programs use up a "slot" in the memory when running and do not instantly release that slot when closed. If too many slots are filled, you get a memory error.
We suggest that you uninstall any version of the program that may appear in your Add/Remove Programs list; click YES to remove the shared files that prompt for a response. Reboot your system and return to the download link. Before installing, "End Task" any other programs that are running in the background (firewalls, antivirus, cookie blockers, etc.) by hitting the CTRL + ALT + DELETE keys.
RUNTIME ERROR 13:"Type mismatch" means that you do not have the English (United States) setting in your Regional Settings.
Change Regional Settings to English (United States) under My Computer / Control Panel / Regional Settings
RUNTIME ERROR 48:There is a .dll file conflict, which means that some other program is probably using the same file. Disable all other programs that may be running in the background (anti-virus, download managers, Instant Messengers, etc.), then reinstall the program.
RUNTIME ERROR 75: "Run-time error 75: path/file access error." This error occurs when a program is installed on a network and the user does not have rights to the program directory. For the program to work properly on a network, users must be given rights by the network administrator.
RUN TIME ERROR 339:You cannot log in to the program. You receive the message "Component "file name" or one of its dependencies not currently registered: a file is missing or invalid."Below are the 2 examples of 339 error messages our customers have received. I. I am getting a Runtime Error 339: "Missing File"... The files most commonly missing or incorrectly registered are listed below: VSFLEX7L.OCX ctLstBar.ocx GTProgss.ocx II. I am getting a Runtime Error 339 "File Missing or Incorrectly Registered"...
Previously in Net Detective 7.0 (the first few releases .01 -.09 first edition prior to April 4, 2002): These errors were due to ActiveX controls that were out of date. Uninstalling completely and installing the most current version of ND resolves this issue. A Windows Update from Microsoft.com replaces outdated files as well. Uninstall our program, do a Windows update, reboot, then redownload.
RUNTIME ERROR 372:Failed to load control CommonDialog from "filename".OCX - your version of the .OCX file may be outdated. Or Run-time error "372" Failed to load control "MS Comm" from MSCOMM32.OCX. Your version of MSCOMM32.OCX may be outdated. Make sure you are using the version of the control that was provided with your application. Or OLEAUT32.dll is out of date. A newer version is required for this program. Indicates that the common control needs to be updated.
FIRST: Try searching for the file then renaming the Mswinsck.ocx (for example OldMswinsck.ocx), and reinstalling the program and choose Repair. WHEN ALL ELSE FAILS: 1. Identify the name of the control by reading the error message. Controls have file names that end in "OCX" or "DLL". Write down the name of the control. 2. Open an MS-DOS window by clicking "Start," drag to "Programs," then click on "MS-DOS Prompt." This will open the "MS-DOS Prompt" window. You should see a C:\WINDOWS> prompt. 3. Type "cd system" (do not type the quotation marks) and press This will change the prompt to C:\WINDOWS\SYSTEM>. 4. Rename the older version of the control identified in step 1 by typing "ren control control.old" for example "ren comdlg32.ocx comdlg32.old" and press (again, do not type the quotation marks.) 5. If your Run Time Error message specifies a different file, replace "comdlg32" with your specified file.] This will rename the file and return the prompt to C:\WINDOWS\SYSTEM>. 6. Close the "MS-DOS Prompt" window by clicking the X button in the top right corner. 7. Download the control updates from Microsoft for your system type under "Windows".
RUNTIME ERROR 373:"Error: 373 no such interface supported in Internet Explorer" This error occurs when the jscript.dll file is corrupted or damaged. Use the System file checker to extract a new copy of jscript.dll from their Windows cd. You can try to do a Windows & IE update. (Source: http://support.earthlink.net/mu/1/psc/img/walkthroughs/windows_9x_nt/browsers/ie_4.0/2036.psc.html)
RUNTIME ERROR 374:After running the setup.exe you receive a run-time error: '374' Fail to activate control "VB.User Control". The control may not be the correct version. Make sure you have the most recent updates for Windows and Internet Explorer, restart, then try to run the setup again.