Registering OCX Control

Topic

New Reply

I am Trying to create a form within Excel 2000 and I am Trying to add the common dialog control to the form. I have added the control to the toolbox but when inserting the control on the form I get a message stating that the “Control could not be created because it is not properly licensed”.
Can someone please tell me how to license the comdlg32.ocx control as this is driving me nuts!
Thanks in advance.
Brian.

Reply | Quote

Replies

Brian,

I used to get this message when playing around with addl. controls in Office 97 – my understanding was that this was because I did not have VB5 installed on my machine.

In Office 2000 I’ve got the Developer’s Edition (or whatever the precise name is) and I find I can access the additional controls with no problems (just have to learn how to use ’em now).
So my guess is you need either VB6 or the Office2000 Dev Edition.

Gary

Reply | Quote

Your guess is correct, you have to have the MOD/ODE or VB Professional installed to have a license to develop with and redistribute the OCXs that come with Office. Otherwise, they’re teases. And if you just copy a custom application (Excel workbook, Access database, whatever) to another machine, they’ll get the same nasty message unless they already have a license.

Reply | Quote

Thanks, Charlotte.
A further question, just so I understand it clearly. Since I have a licensed copy of MOD/ODE, as you say I should be able to develop with and redistribute the OCXs.

Do all the other users in my office then need to have the license on their machines (or to put it another way, do their networked applications need to have the licenses), in order to use something I’ve developed on my machine?

BTW speaking of teases, unless I didn’t install Office right, although I now have access to the controls, I don’t have the online VB help on how to use them – I guess I have to get VB6 for that!

Reply | Quote

It depends on the OCX whether it’s redistributable. You’ll have to check the MOD documentation on that one. I never use the blasted things because of all the trouble they are to distribute. Howver, if you create a setup using the Packaging and Deployment Wizard that comes with MOD and VB Pro, you create an installation package that will install and (should) register any redistributable OCXs on the target machines.

Actually, the online help is all that useful. If you open the form in design view, open the properties dialog of the OCX and get to the tab that contains the properties unique to that control, you can get some help using F1. Your best bet is to get a copy of the O’Reilly book, Visual Basic Controls in a Nutshell.

Reply | Quote

Good stuff. Thanks again for this additional info.

Gary

Reply | Quote

Brian,

Do you need th common control on your form?

In Excel, I’ve always used something like”

dlgAnswer = Application.Dialogs(xlDialogOpen).Show

I don’t need the common dialog control as I do in VB, and I haven’t had to worry about comctl32.ocx or the like

Reply | Quote