Runtime error 380 is more commonly characterised by a message that will display an 'invalid property value' dialogue on your computer. Runtime errors are in essence, problems Windows encountered when trying to link the chain of instructions that allow for the successful execution of a program when loaded. Programmers who designed programs will often encounter instances in various different situations where files are missing and commands are not followed to the T. While they will try their best to control these problems and print out an almost perfect piece of published software, they can never compensate for the literally millions of hardware and software configurations out in the wild world of computing.
Runtime Error 380 is simply a code that tells you a certain link in the chain is damaged or corrupted, unable to complete the commands that would allow whatever it is you are trying to do to load. In this case, it is usually a problem with root names and corruptions/problems within the Visual Basics directory. Technophiles might be able to get around the problem by locking in on the program that has the error and repairing the damage (which sometimes just needs either renaming of certain files and command lines/directories). Sometimes, error 380 also could mean that a program is running with pre conceptions of older versions of .OCX files within the Visual Basics Library - and your computer just happens to be running a much later version.
An update either way will help you to resolve this situation. OR the cause might be an outdated .DLL file (or missing) within Microsoft Visual Basic 4.0 - 5.0 Professional/Enterprise editions. As you can see, the root causes of the 380 are quite varied and for the casual user, this will be more than just a mere inconvenience. A quick look online will reveal even more possibilities, so as I write this, I realise as well that the problems listed here could be just the tip of the ice berg. Instead of instructing you on how to solve it with specific details, I will advise all who come across this problem to first look at the registry. Now, if you have no idea about how the registry works, then I advise you to not go in unschooled and try to modify the keys and command lines within its matrix.
Always, always use a registry cleaner that has been designed to rifle through the information with its delicate tools and clean any problems or bad data within the registry. Most of the time, runtime errors like this one is due to null values, orphan data keys and bad program command lines within the registry, either caused by time/use and attacks of intrusive and malicious software. Because Windows depends on the registry to tell it what to do, you need to clean out your registry to nullify problems like runtime error 380. Not only will it go away, but you will find yourself with a faster PC then what you started with, and that is good value.