daimler
asked on
comctl.ocx problem
I posted the following on usenet and received no reply, can someone help please....
I recently acquired VB4 and I am having the following problem....
When I try and include any of the comctl bits (slider etc) I get the
following error message...
"License information for this component not found. You do not have an
appropriate license to use this funtionality in the design
environment"
I thought these bits were standard windows95 controls so I assumed I
had them. I certainly have comctl.ocx in \windows\system so what am I
missing (keep it clean)
tia
Ken
I recently acquired VB4 and I am having the following problem....
When I try and include any of the comctl bits (slider etc) I get the
following error message...
"License information for this component not found. You do not have an
appropriate license to use this funtionality in the design
environment"
I thought these bits were standard windows95 controls so I assumed I
had them. I certainly have comctl.ocx in \windows\system so what am I
missing (keep it clean)
tia
Ken
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
P.S. the first version of VB4 was really buggy, mostly in all the new controls in ComCtl. I hope you got the 4.0a version. If not you'll be pulling your hair out over RDO and Treeview/ListView bugs!
ASKER
Thanks for your suggestion. I have tried it but without success. Perhaps the following
extra information will help pinpoint the problem.
1. There was no reference to Microsoft Visual Basic in the Add/Remove Programs dialogue box
so I removed the VB directory/subdirs manualy and moved the OCX files to a safe location.
2. When I installed I got the following message towards the end of the install process....
"VBCustom_Controls_Actions _Reg_graph was unable to register itself in the system registry"
(This may have happened on the original install - I can't remember)
3. I checked the VB.ini file in c:\Windows and it has the following entry....
"OCXRegister=0"
4. When I start up VB I get the error msg....
"msrdc32.ocx could cot be loaded -- Continue Loading Project?"
5. The source of my VB4 cd could be said (politely) to be 'suspect'.
Should I give up now and try and obtain a less 'suspect' copy. Everything works except the
extra windows95 controls.
Do I need to remove all references to these from the system registry? (which could be dangerous)
I think that you will earn a lot of points if you can sort this out :-)
Cheers
extra information will help pinpoint the problem.
1. There was no reference to Microsoft Visual Basic in the Add/Remove Programs dialogue box
so I removed the VB directory/subdirs manualy and moved the OCX files to a safe location.
2. When I installed I got the following message towards the end of the install process....
"VBCustom_Controls_Actions
(This may have happened on the original install - I can't remember)
3. I checked the VB.ini file in c:\Windows and it has the following entry....
"OCXRegister=0"
4. When I start up VB I get the error msg....
"msrdc32.ocx could cot be loaded -- Continue Loading Project?"
5. The source of my VB4 cd could be said (politely) to be 'suspect'.
Should I give up now and try and obtain a less 'suspect' copy. Everything works except the
extra windows95 controls.
Do I need to remove all references to these from the system registry? (which could be dangerous)
I think that you will earn a lot of points if you can sort this out :-)
Cheers
ASKER
I bought the official release CD of VB 4.0 and got exactly the
same installation problem. I solved it by getting a list of ALL
the 32-bit OCA, OCX and DLL files on the CD (directory:vb/system)
and removing them from my windows/system directory. VB4 then
installed OK and seems to be fully functional.
Thanks for your help.
same installation problem. I solved it by getting a list of ALL
the 32-bit OCA, OCX and DLL files on the CD (directory:vb/system)
and removing them from my windows/system directory. VB4 then
installed OK and seems to be fully functional.
Thanks for your help.