Link to home
Start Free TrialLog in
Avatar of mwielgus
mwielgusFlag for United States of America

asked on

Removing a charting control

I have a VB6 application that was created with Olectra chart.  For some reason, under Win 2K, it will no longer compile, and I cannot figure out how to remove the control.  I have re-installed the 32-bit application (v5.02), and tried to remove every reference to the control that I can find, but VB will not allow me to remove the control from the project.  How do I get rid of this thing, or get it to allow me to compile the application with it included in the project?
I have registered the control using regsvr32, but that does no good.
Avatar of wuerzi
wuerzi
Flag of Germany image

1. Save all your files!!!
2. open your project-file with notepad or an other editor
3. drop the line 'Object=...' which ends with the *FileName* of your Chart-Control
4. Save and close file
5. Open the project with VB
6. You will get an error, if you open a form or conrol, wich still have a reference to the chart-control
7. VB converts this old chart-control to a picturebox
Avatar of mwielgus

ASKER

I still get the Microsoft Visual Basic error message "License information for this component not found.  You do not have an appropriate license to use this functionality in the design environment" and the chart control is the only non-MS control that is used.  I know that I have a license to use the chart control.
Did you develop the app on a different box?  If so, that is the box with the license.

J.
I don't understand.  I did build the software on a different box, but that was a different one from the one that was used to create the original software.  I re-installed the control on my current desktop.  Why doesn't that make the license valid?
Depends what the registration process was like.  If it was just a case of tapping in a serial, then it should be fine, but if the process then connected to the Internet and checked that serial against an online record, it might not like the use of the control on more than one registered machine, or maybe each serial only allows a certain no of registrations.

Either that, or maybe the control is corrupt, or is missing some dependancies...

J.
I found an article in the Microsoft Knowledge Base that recommends installing the latest service pack for VB 6.  The problem is caused, according to MS, by installing an app that contains a control, then installing VB 6, and trying to do development using that control.  This is what happened to me.  If the service pack works, then I will recommend closing this question.
MS Knowledge Base article 177799 recommends running vbctrls.reg from the Visual Studio or VB6 installation CDs.  I did this, and no longer have the problem.  I recommend deleting this question.
I reckon this should be PAQ'd for anyone else who may experience this issue.  Post a request in CS.

J.
Fine by me.
ASKER CERTIFIED SOLUTION
Avatar of PAQ_Man
PAQ_Man
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial