[RESOLVED] vb6 controls in VBA

How can I use vb6 controls (msdatagrid for example) with VBA without having VB6 installed (get licensing error otherwise)?

Are there any similar grid controls for VBA available that are very cheap or free?

If you click on the additional tools button on the toolbox you can "import" whatever controls you have registered on your system. You can also install the vb 6 runtime redistributable too as your VBA users will need it installed to view your userform if you plan on distributing it.

Thanks for the response. The problem is that if you dont have VB6 on your machine you wont have an msdatagrid registered (the control will be there, but it will complain about no license and die if you try to use it).

I was hoping there might be a way to license those vb6 primitive controls that ship with VBA but not vb6.

You can register the control silently with the /s switch.

Quote:

---

Originally Posted by RobDog888

You can register the control silently with the /s switch.

---

so this will solve the problem?

Start - Run - regsvr32.exe /s MSDATGRD.OCX

Im skeptical, but will get the person I am working with to try it (I haven't got a machine without VB6 installed)

The reason I am skeptical is that it is a design time licensing issue ... not a registration issue as far as I know. using regsvr.exe doesnt work (using no switches) so I dont understand why the silent switch would change anything.

Thanks for the response!

Quote:

---

The problem is that if you dont have VB6 on your machine you wont have an msdatagrid registered

---

Im going off of that statement as if you loaded the ocx and registered it then it would be logical that the licensing issue would disappear.

If having just the single ocx installed and registered wont prevent the licensing issue before you open Excel then perhaps installing the entire runtime redistributable would suffice?

Quote:

---

Originally Posted by RobDog888

Im going off of that statement as if you loaded the ocx and registered it then it would be logical that the licensing issue would disappear.

If having just the single ocx installed and registered wont prevent the licensing issue before you open Excel then perhaps installing the entire runtime redistributable would suffice?

---

Turns out it's a licensing issue. without vb6 installed there is no design time license (although the runtime license exists) for the grid and it cannot be used in excel macros. I finally got what I needed by building a vb6 ocx wrapper with the props I needed.

Thanks for the responses!

Thanks for the update. Interesting issue though. Too bad MS just didnt allow the runtime controls to be used in VBA designers.