Licensing Issue with Rich Text Box (I Think)

[Golom]

I have a small application that I've been attempting to install on other machines. They are all XP-Pro laptops that have a third-party Web-Based application installed. That application requires that the .NET 2.0 framework be installed followed by a download of the various application components (DLLs, EXEs, Database files, etc.) for the Web application.

When I install my small VB6 application on these machines I get the message

[blue]You do not have a license to use this control.[/blue]

when I attempt to open any form that includes a rich text box. This doesn't happen on my own laptop that also has the Web application installed. It does however, also have VB6 installed.

I have grazed about and found issues where VS6 RTB licensing is an issue with a Visual Studio .NET development environment. I have found nothing to indicate that there is some run-time license requirement for a Rich Text Box beyond merely registering it.

The installation is a VS/Installer (.msi) project and I'm putting everything in the application directory (i.e. I'm not doing anything to the Windows, Windows\System or Windows\System32 directories.)

The Questions

Is there something special that I need to do to include licensing information with the install?

Is it possible that the .Net 2.0 framework is interfering with the licensing for this component?

Could the third-party Web application be creating a conflict when I'm attempting to register my own versions of riched32.dll and richtx32.ocx?

 

[TomKane]

Hi,

I saw this - it looks related to your issue.

Regards,
Tom

http://support.microsoft.com/kb/318597

 

[Golom]

Thanks Tom. I had seen that and it relates to design-time licensing.

I did find out what the problem was however.

It was not Rich Text Box but a third-party calendar control that I use. The calendar control is an OCX but it also requires a DLL that doesn't show up in the references. If you explicitly add a reference to the DLL then everything works. I guess it worked on my machine without that explicit reference in VB because the DLL was already registered by other applications.