Install/Use a VB5 OCX in VB6 ?

[Martin]

I have an old program written in VB-5 on a Win NT computer. The
production installation of the program also runs on an NT box (there's
only one installation of this program).

I want to migrate the source code (for further development) over to a
newer computer that's running XP Pro where my development environment
is VB 6.

I copied the source code over and opened the program in VB6. It
generated an error telling me that MSDBGrid was not a loaded control
class. This is the DBGrid32.OCX which apparently is VB5-only.

Can I get this to work by simply copying the DBGrid32.OCX, .OCA and
.DEP files over from the old computer (and registering them)?

I'm afraid to try anything because I don't want to screw-up my VB6
installation.

Thanks for any advice.

[Jeff Johnson]

Post by Martin
Can I get this to work by simply copying the DBGrid32.OCX, .OCA and
.DEP files over from the old computer (and registering them)?

And registering, yes. And you only need the .OCX, nothing else.

[Martin]

Post by Jeff Johnson

Post by Martin
Can I get this to work by simply copying the DBGrid32.OCX, .OCA and
.DEP files over from the old computer (and registering them)?

And registering, yes. And you only need the .OCX, nothing else.

Thanks, Jeff.

I did that and, yes, it worked!

The compiled version of the program (compiled on the old NT computer)
runs just fine. However, if I try to run it in the editor - or if I
try to re-compile it - I get the error message that says: 'I don't
have an appropriate license to use this functionality' (or words to
that effect).

Any suggestions as to what I need to do to get past this?

Thanks again.

[Ken Halter]

Post by Martin
Thanks, Jeff.
I did that and, yes, it worked!
The compiled version of the program (compiled on the old NT computer)
runs just fine. However, if I try to run it in the editor - or if I
try to re-compile it - I get the error message that says: 'I don't
have an appropriate license to use this functionality' (or words to
that effect).
Any suggestions as to what I need to do to get past this?
Thanks again.

Since, according to the article below, that control ships with VB6,
licensing should already be present....

Controls shipped in Visual Basic 6.0
http://support.microsoft.com/kb/194784/en-us

...but, if it isn't, the utility below /should/ fix the problem, even though
the control doesn't show in the list (strange)

FILE: VB6Cli.exe Fixes License Problems with Visual Basic 6.0
http://support.microsoft.com/kb/194751/EN-US/

[Martin]

On Tue, 11 Sep 2007 14:46:08 -0700, "Ken Halter"

Post by Ken Halter

Post by Martin
Thanks, Jeff.
I did that and, yes, it worked!
The compiled version of the program (compiled on the old NT computer)
runs just fine. However, if I try to run it in the editor - or if I
try to re-compile it - I get the error message that says: 'I don't
have an appropriate license to use this functionality' (or words to
that effect).
Any suggestions as to what I need to do to get past this?
Thanks again.

Since, according to the article below, that control ships with VB6,
licensing should already be present....
Controls shipped in Visual Basic 6.0
http://support.microsoft.com/kb/194784/en-us
...but, if it isn't, the utility below /should/ fix the problem, even though
the control doesn't show in the list (strange)
FILE: VB6Cli.exe Fixes License Problems with Visual Basic 6.0
http://support.microsoft.com/kb/194751/EN-US/

Thanks, Ken.

The referenced article is apprently is wrong. The DBGrid32.OCX is NOT
installed on any of the 3 different computers that I have VB-6 on.
And, of course, it does not appear in the "Components" list in VB-6 on
any of these machines.

After copying over (and registering) the OCX from the VB-5
installation, it does appear in the VB-6 Components list.

I downloaded and ran the VB6Cli utility but it made no difference. I
still get the same "license" error msg.

Is this licensing stuff just an entry in the registry somewhere? Could
I create something manually in the registry to get past this?

[Ralph]

Post by Martin

<snipped>

The referenced article is apprently is wrong. The DBGrid32.OCX is NOT
installed on any of the 3 different computers that I have VB-6 on.
And, of course, it does not appear in the "Components" list in VB-6 on
any of these machines.

It ships with the "Microsoft Visual Studio 6.0 Enterprise Edition" as per
the DLL Help Database...
http://support.microsoft.com/dllhelp/

Post by Martin
After copying over (and registering) the OCX from the VB-5
installation, it does appear in the VB-6 Components list.
I downloaded and ran the VB6Cli utility but it made no difference. I
still get the same "license" error msg.
Is this licensing stuff just an entry in the registry somewhere? Could
I create something manually in the registry to get past this?

It should have worked with the URL Ken provided.
http://support.microsoft.com/kb/194751
Where again are you getting this licensing error?

-ralph

[Martin]

On Tue, 11 Sep 2007 17:50:02 -0500, "Ralph"

Post by Ralph

Post by Martin

<snipped>

The referenced article is apprently is wrong. The DBGrid32.OCX is NOT
installed on any of the 3 different computers that I have VB-6 on.
And, of course, it does not appear in the "Components" list in VB-6 on
any of these machines.

It ships with the "Microsoft Visual Studio 6.0 Enterprise Edition" as per
the DLL Help Database...
http://support.microsoft.com/dllhelp/

Apparently, I do not have "Visual Studio". My CD's are labeled:
Microsoft Visual Basic 6.0 Enterprise Edition Development System.

FWIW, the grid control that is installed on my VB-6 computers is
MSDATGRD.OCX

Post by Ralph

Post by Martin
After copying over (and registering) the OCX from the VB-5
installation, it does appear in the VB-6 Components list.
I downloaded and ran the VB6Cli utility but it made no difference. I
still get the same "license" error msg.
Is this licensing stuff just an entry in the registry somewhere? Could
I create something manually in the registry to get past this?

It should have worked with the URL Ken provided.
http://support.microsoft.com/kb/194751
Where again are you getting this licensing error?

When I try to run the program in the VB-6 editor. Or when I try to
compile the program.

[Ralph]

Post by Martin
On Tue, 11 Sep 2007 17:50:02 -0500, "Ralph"

I should have said ... "Microsoft Visual Studio 6.0 Enterprise Edition" or
"Microsoft Visual Basic 6.0 Enterprise Edition"

Anyway MikeD's advice should have you on course. The exact location will
vary - but its there alone with the lic file somewhere. <g>

-ralph

[Randy Birch]

Appropriate licensing for VB5 controls is installed when VB5 is installed.
If this is not done, it is the same as if a general user tried to use the
control in a VB or VBA development environment - not licensed, so you get
the error. The license fix tool repairs a damaged registry that sometimes
occurred when program updates were installed. It will do nada on a control
that is not installed as part of the dev environment.

You can safely install VB5 on the same box as VB6 - just pick different
directories. Usually recommended to do the VB5 install first, but it won't
be a prob.
--
Randy Birch
MS MVP, Visual Basic
http://vbnet.mvps.org/

Please respond to the newsgroups so all can benefit.


"Martin" <***@comcast.net> wrote in message news:***@4ax.com...
On Tue, 11 Sep 2007 17:50:02 -0500, "Ralph"

Post by Ralph

Post by Martin

<snipped>

The referenced article is apprently is wrong. The DBGrid32.OCX is NOT
installed on any of the 3 different computers that I have VB-6 on.
And, of course, it does not appear in the "Components" list in VB-6 on
any of these machines.

It ships with the "Microsoft Visual Studio 6.0 Enterprise Edition" as per
the DLL Help Database...
http://support.microsoft.com/dllhelp/

Apparently, I do not have "Visual Studio". My CD's are labeled:
Microsoft Visual Basic 6.0 Enterprise Edition Development System.

FWIW, the grid control that is installed on my VB-6 computers is
MSDATGRD.OCX

Post by Ralph

Post by Martin
After copying over (and registering) the OCX from the VB-5
installation, it does appear in the VB-6 Components list.
I downloaded and ran the VB6Cli utility but it made no difference. I
still get the same "license" error msg.
Is this licensing stuff just an entry in the registry somewhere? Could
I create something manually in the registry to get past this?

It should have worked with the URL Ken provided.
http://support.microsoft.com/kb/194751
Where again are you getting this licensing error?

When I try to run the program in the VB-6 editor. Or when I try to
compile the program.

[MikeD]

Post by Martin
The referenced article is apprently is wrong. The DBGrid32.OCX is NOT
installed on any of the 3 different computers that I have VB-6 on.
And, of course, it does not appear in the "Components" list in VB-6 on
any of these machines.
After copying over (and registering) the OCX from the VB-5
installation, it does appear in the VB-6 Components list.
I downloaded and ran the VB6Cli utility but it made no difference. I
still get the same "license" error msg.
Is this licensing stuff just an entry in the registry somewhere? Could
I create something manually in the registry to get past this?

Look on your VB6 Enterprise discs for the following path:

Z:\COMMON\TOOLS\VB\CONTROLS

(where Z: is your CD or DVD drive)

This path should be on disc 1 of VB6 Enterprise (I have ISO images of that
and double-checked it).

In this folder, you'll find the control AND a .reg file that contains the
design-time license information. There's also a README file that I would
strongly advise you open and read.

[Martin]

Post by MikeD
Z:\COMMON\TOOLS\VB\CONTROLS
(where Z: is your CD or DVD drive)
This path should be on disc 1 of VB6 Enterprise (I have ISO images of that
and double-checked it).
In this folder, you'll find the control AND a .reg file that contains the
design-time license information. There's also a README file that I would
strongly advise you open and read.

Jeff / Mike / Ralph / Ken / Randy: Thank you, thank you, thank you !!

I followed the instructions in the ReadMe file on the CD and
everything works like it's supposed to !