Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
ComCtl32.ocx will not register
Message
De
19/03/1998 12:33:31
 
 
À
19/03/1998 12:20:59
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00085369
Message ID:
00085713
Vues:
31
Hi Dore.

No VB5 on my machine. I can access all this stuff fine in the VFP environment. It is in my distributed app that I am having the problem. And I can't find anything to fix this! I'm getting ready for a nervous breakdown.

Marcia

>By any chance have you installed the Microsoft Visual Basic Version 5 Control Creation Edition, especially an early beta of it?. When I did I had similar problems accessing controls in comctl32. It took a reinstall of VFP to clear up the problem. Then when I installed a later version of the VB5CCE there was no similar occurrance of the problem.
>-Dore
>
>>>Hi all.
>>>
>>>I have an application that uses the TreeView. I have ComCtl32.* in my distribution tree. I have it marked as ActiveX in the setup wizard. But I have machines that will not register it during the installation. I have a comctl32.reg file that I created, and after running that, it still is not registered. Can anyone help me out here?
>>>
>>>TIA
>>>
>>>Marcia
>>
>>I have possibly the same problem. When I try to run a form that uses the TREEVIEW it complains that the control is NOT reqistered.The only help I have been able to find is the following :
>>
>>**There is known bug in the setup wiz that the control file (COMCTL32) must be in the ROOT directory of the distribution directory itself.**
>>
>>This does not explain my problem, but it may help you. In my case the control appears correctly registered. Even if I manually use REGSVR32 the form will not run. The only guess I can make is that a previous version of the control that was registered on the destination was not properly overwritten. On such PC's where I manually unregistered the existing control first I have not had any problems. I did come across a new group that contained 2 messages showing similar problems, but they had no solutions!
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform