License Information for This Component Not Found

23 May 2005 11:21 PM

Jon in Canby Or.

Thanks to a machine crashing I've had to reinstall VB6 on a new machine and a
backup of my projects. One project gets this error when trying to "make" the
executable with the message noted in the subject of this posting.

I think I've tracked down the difference. On the old machine I had Office XP
Pro and on the new one I have Office 2003. This project references the
Microsoft Word Object Library. On the old machine it was the 10.0 library, on
the new one it's now the 11.0 library (MSWORD.OLB). I've checked the
knowledge base and got some information on the problem but not enough clues
to help me overcome it. Does anybody know what's going on and more
importantly does anybody know how I can solve this?

Cheers,
Jon

24 May 2005 12:04 AM

Veign

That's the difference (Office versions) but is that the component causing
the problem?.

Try:

FILE: VB5cli.exe Fixes Visual Basic 5.0 Control Installation Problem
http://support.microsoft.com/kb/q181854/

FILE: VB6Cli.exe Fixes License Problems with Visual Basic 6.0
http://support.microsoft.com/default.aspx?scid=kb;EN-US;194751

--
Chris Hanscom - Microsoft MVP (VB)
Veign's Resource Center
http://www.veign.com/vrc_main.asp
--
Read. Decide. Sign the petition to Microsoft.
http://classicvb.org/petition/

Show quoteHide quote

"Jon in Canby Or." <JoninCanb***@discussions.microsoft.com> wrote in message
news:A3EF35AF-E305-4F7D-A144-21111ED23201@microsoft.com...
> Thanks to a machine crashing I've had to reinstall VB6 on a new machine
and a
> backup of my projects. One project gets this error when trying to "make"
the
> executable with the message noted in the subject of this posting.
>
> I think I've tracked down the difference. On the old machine I had Office
XP
> Pro and on the new one I have Office 2003. This project references the
> Microsoft Word Object Library. On the old machine it was the 10.0 library,
on
> the new one it's now the 11.0 library (MSWORD.OLB). I've checked the
> knowledge base and got some information on the problem but not enough
clues
> to help me overcome it. Does anybody know what's going on and more
> importantly does anybody know how I can solve this?
>
> Cheers,
> Jon

24 May 2005 12:44 AM

Jon in Canby Or.

Thanks, VB6Cli solved the problem.

Show quoteHide quote

"Veign" wrote:

> That's the difference (Office versions) but is that the component causing
> the problem?.
>
> Try:
>
> FILE: VB5cli.exe Fixes Visual Basic 5.0 Control Installation Problem
> http://support.microsoft.com/kb/q181854/
>
> FILE: VB6Cli.exe Fixes License Problems with Visual Basic 6.0
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;194751
>
> --
> Chris Hanscom - Microsoft MVP (VB)
> Veign's Resource Center
> http://www.veign.com/vrc_main.asp
> --
> Read. Decide. Sign the petition to Microsoft.
> http://classicvb.org/petition/
>
>
> "Jon in Canby Or." <JoninCanb***@discussions.microsoft.com> wrote in message
> news:A3EF35AF-E305-4F7D-A144-21111ED23201@microsoft.com...
> > Thanks to a machine crashing I've had to reinstall VB6 on a new machine
> and a
> > backup of my projects. One project gets this error when trying to "make"
> the
> > executable with the message noted in the subject of this posting.
> >
> > I think I've tracked down the difference. On the old machine I had Office
> XP
> > Pro and on the new one I have Office 2003. This project references the
> > Microsoft Word Object Library. On the old machine it was the 10.0 library,
> on
> > the new one it's now the 11.0 library (MSWORD.OLB). I've checked the
> > knowledge base and got some information on the problem but not enough
> clues
> > to help me overcome it. Does anybody know what's going on and more
> > importantly does anybody know how I can solve this?
> >
> > Cheers,
> > Jon
>
>
>