If you’ve got a runtime error 80010108, your solution is either really easy or it is really difficult. If an necessary ActiveX object can not be located, this error comes up. An ActiveX object on vacation is not precisely an unusual problem for the tech support group.
When an ActiveX object is created, it is generally supported by the program you are drawing on. Let’s suppose you need to routinely export data from Excel in to Visual Basic and you hope to automate that task. Beginning in Excel, you delineate the limits for the data export and when you are finished you shut Excel down. You are working with Visual Basic as you see the runtime error 80010108 “the object invoked has disconnected from its clients” message. This means that the “client” (Visual Basic) tried to summon the ActiveX object (the data from Excel), but the object was unavailable.
The typical reason for your runtime error 80010108? Excel (in our scenario) must be running in order to sustain the ActiveX object Visual Basic wants to access. As for our example, that tells you Excel has to be live in order to create an automated task into Visual Basic.
If the preceding advice ends your runtime error 80010108 consider yourself blessed. ActiveX object problems can become awfully involved, but they frequently originate in out of date, unregistered, or corrupt files in the Windows registry. Where to begin? Fundamental computer care. Retrieve every update for Microsoft Windows and find all available patches or hot fixes for your particular programs, as well. It could be a hassle to track them down, but updates frequently resolve incompatibility problems within your system, which is the typical source of a runtime error. Updates will let you know that your computer features the most current ActiveX supporting DLLs available.
If getting all the updates does not resolve the error, the next recommended step is to run your anti-virus program on a full diagnostic of your system. Next run the best registry repair software to register your DLLs, fix ActiveX-related problems, and eliminate the gummy junk inside your PC’s registry. Since lots of operating system troubles come from registry damage, having a registry cleaner in your maintenance kit is a good preventative measure. I recommend running the complimentary diagnostic scan that most registry cleaner programs give before you decide to buy so that you can be certain that the program will address your specific problem. (Be sure the specific registry cleaner can help you before you buy it!)
If applying any or all of the above advice solved your runtime error 80010108, then you are actually fortunate. But there is always the worst case scenario. There’s no shame in hiring a PC repair pro to dig into your system to locate the problem if you’ve made a reasonable effort to trouble shoot it yourself. Many times programmers writing code get the runtime error 80010108 and the repair is always painful because the “disconnection” occurs due to a small error in one line of their program. (Seems like a unique hell of editing, really.) Here’s hoping your error is triggered by the easiest mistake: Is the program that supports your “disconnected” object turned on?