If you’ve got a runtime error 80010108, your remedy is either really easy or it is extremely difficult. The error happens when an ActiveX object being inaccessible for some reason. An ActiveX object disconnect is not exactly an unusual problem for computer users everywhere.
Frequently the reason the ActiveX object is not correctly found is because you turned off the program that sustains the object. For instance, imagine you need to automate the export of some data from an Excel spreadsheet in to Visual Basic. You start your labor inside Excel defining the chosen data for the task and when you are finished, you shut Excel down. You are struggling with Visual Basic when you get the runtime error 80010108 “the object invoked has disconnected from its clients” popup. Visual Basic is the “client” and the “object” is the automation job supported from Excel.
The most common reason for the runtime error 80010108? You turned Excel (our example) off and Excel supports the ActiveX object invoked. To sustain the connection with the needed object, you need to have the application it came from running. In our example, that means Excel can’t be shut down if you need to automate an export out of Excel into Visual Basic.
You really caught a break if that was the source of your runtime error 80010108. The complexity of triggers for ActiveX object errors rises steeply from here – maybe it is a DLL problem or the ubiquitous malware in the registry possibility. A smart place to start is with basic computer care. There is no better time to gather all the Microsoft Windows updates and to track down patches for the individual applications on your PC. Since a lot of runtime errors arise from incompatibility between applications or within the system, getting updates is generally smart. To get the up to date DLLs and object instructions, you need to update constantly.
When you are still getting the error message even after the updates, then pull out your anti-malware utility and give your PC a full inspection for malware. Next run the best registry repair software to re-register your DLLs, fix ActiveX-related problems, and clean off the glue-like garbage inside your computer’s registry. Registry cleaners specialize in repairing registry cluttering that instigates runtime errors such as the runtime error 80010108. The good registry cleaners supply a free scan so you can tell if the utility will be able to address your specific problem. (Why buy a software that can’t help you, right?)
I wish the preceding steps would end everyone’s runtime error 80010108. Yet there is always that worst case scenario. There isn’t any shame in getting a PC repair pro to delve into your operating system to locate the problem if you’ve made a serious effort to trouble shoot it yourself. The runtime error 80010108 can be actually a plague – programmers experience it sometimes and it requires lots of miserable editing to resolve it. Hopefully the cause of your runtime error won’t be so difficult to uncover!
