Microsoft common dialog activex

Since copying the application to XP, when I try to insert a new CommonDialog object onto a form I get the following error message. To obtain the appropriate license, contact the company that provides the licensed OLE object or ActiveX control". This application and adding new common dialog controls works fine on my NT machine. On the XP machine I can't insert a new common dialog control.

I tried unregistering and re-registering the ActiveX control, no luck. I tried registering the OCX using regsvr32, nothing.

I am using Access but the same error occurs on Access The comdlg The really odd thing is that the application runs on my machine with the common dialog opening properly, I just can't add a new control. On another machine it will not even open the common dialog says it can't find the object and gives the same No License error when trying to add the object onto the form.

It's not as if the control is completely missing or not registered. The control exists but does not behave correctly as events are not firing correctly. For instance, the Treeview control don't issue NodeClick events, so any code that expects the expansion of a node to display or load more data fails.

It took us a while to discover that a change in this control caused this problem. In other cases, users are reporting that Microsoft Access locks up and crashes. People are also reporting problems with this in Visual Basic 6 VB6 applications. Here are additional reports of issues associated with this patch.

This impacts our Total Access Analyzer product which displays the results of your Microsoft Access database documentation with the Treeview control. This error appears:. If your PC received the security update and you're using the Microsoft Access , , , , or version of Total Access Analyzer, the Treeview control in our Database Explorer view no longer functions properly. Microsoft has acknowledged problems with their security update that is causing these problems.

OCX file. Microsoft has released a Knowledgebase article addressing this problem entitled: MS Description of the security update for Office system: August 14, In our internal testing, we've discovered that the recommended steps don't work in most cases. Just unregistering and re-registering the control doesn't solve the problem.

We tried adding a reboot between steps, but that didn't help either. The steps below work consistently. An technical explanation why is given at the end. While there seems to be nothing physically wrong with the new OCX, we need to register another version to reset it.

Here are the steps we discovered to manually repair this issue reliably and consistently:. You need Administrator rights to make registry changes. Depending on your operating system and Windows login rights, you may not be allowed to do this. With your subscription - you'll gain access to our exclusive IT community of thousands of IT pros. We can't always guarantee that the perfect solution to your specific problem will be waiting for you. If you ask your own question - our Certified Experts will team up with you to help you get the answers you need.

Who are the certified experts? How quickly will I get my solution? We can't guarantee quick solutions - Experts Exchange isn't a help desk. We're a community of IT professionals committed to sharing knowledge. On the Format tab, click the down arrow below View , and then click Design View. Click the Event tab, click [Event Procedure] in the On Click list, and then click the ellipsis button On the Insert menu, click Module , and then insert code that resembles the following code example into Module1.

On the Format tab, click the down arrow below View , and then click Form View. Skip to main content. This browser is no longer supported.

Download Microsoft Edge More info.