I have tried for two days to register grid32.ocx with Regsvr32 but to no
avail. Every time when I want to put the grid control on a userform, it comes
up with: "The control could not be created because it is not properly
licensed". I have also tried to register it through the control toolbar/more
controls/register custom control but also to no avail. I run WinXP Pro and
Office Small Business Edition 2003.
Any help is greatly appreciated

Have a look here for trouble-shooting.

Might be some help?

http://www.ufti.com/faq5.htm

Gord Dibben Excel MVP

On Wed, 8 Dec 2004 13:01:06 -0800, jolivanes
wrote:

I have tried for two days to register grid32.ocx with Regsvr32 but to no
avail. Every time when I want to put the grid control on a userform, it comes
up with: "The control could not be created because it is not properly
licensed". I have also tried to register it through the control toolbar/more
controls/register custom control but also to no avail. I run WinXP Pro and
Office Small Business Edition 2003.
Any help is greatly appreciated

Hi

I don't know what application Grid32.ocx comes with, but I have office xp
pro, win xp Pro and vb6 and it is not on my system. I do have dbgrid32.ocx.

If it comes with a program like visual C+ or something like that, then you
have to have a licensed version of that program on your system before you
can use it with other programs on your system. It still won't work on other
systems you distribute it to unless the application was created by the
licensed program.

For example, say you install a program you bought like ABC.exe and it comes
with an ocx file called maskinput.ocx . You create a program using abc.exe
and use maskinput.ocx as part of the program. If you distribute that
program, it will work fine on any system. Also, you may find that
maskinput.ocx now works with excel VBA on your system. If however, you
create and excel vba program using maskinput.ocx and distribute it to
others, you will probably find out that it will not work on their due to a
licensing problem and if they try to use it in their own excel vba project,
the same license problem will arise.

The parent program usually installs some sort of license file and looks for
that file when you try to use the ocx file. It could have been installed on
your system with an application created by someone who had a license to use
and distribute that ocx file.It would then work on your system with that
application, but not in any applications you create that you try to use it
in. At least, that has been my experience with a lot of (but not all)
commercial ocx files.


HTH

Ken