What is Run Time Error 380? How Can I Fix This Error?

Almost every person using the Microsoft Windows Operating System frequently gets to see annoying pop up messages on their computer screen - this is what Microsoft terms a runtime error. The computer alerts the user of the occurrence of a runtime error whenever a program that is run has an issue with resources or with parameters invoked. Runtime errors are thus dynamic in nature and would depend on the condition of a system at any given time.

Runtime error 380 is frequently accompanied by a message from the system that an Invalid Property Value has been detected when a program is run. This means that a program invocation has been unsuccessful, as Windows has detected an issue while trying to link up several instructions that are used to run the desired program. This is often a result of missing or damaged files, or a missed or incorrect command.

Users of Visual Basic on Windows platform - especially those using Microsoft Visual Basic (Professional and Enterprise Edition) versions 4.0 and 5.0, frequently report Runtime error 380. This is because a Mask Edit Control Value is set as False instead of being set as True at design time. It may be required to have an appropriate version of the files MSMASK32.OCX and VB40032.DLL in addition to making the modification mentioned above.

Runtime error 380 has been acknowledged by the software vendor as a bug in the versions of Visual Basic mentioned above. Microsoft offers a systematic work around for this problem on their support website for the advanced users of Visual Basic.

If you do not use Visual Basic or are unsure as to whether the program that fails to start due to runtime error 380 uses Visual Basic, you can try one of two things -

- Insufficient Memory - The availability of free memory or RAM in your machine may be at a very low level due to too many programs instances running. Close some of the unused programs or low priority programs in order to free up memory and try running the program. The error would not occur again if system memory were the issue.

- Registry Errors - Registry errors may sometimes cause erratic program behavior and prevent programs from starting successfully. A registry scan for errors would be a good action to perform now as any runtime errors arising from registry errors could be fixed.