mscomctl.ocx Windows 7

[D Willett]

Hi. My pc died and went to heaven... came back reincarnated as a windows 7 pc.
In the meantime, my VB6 project won't load MSCOMCTL.ocx and says it is unregistered. I see it in the SysWOW folder and have registered it with Regsvr32 which said it was successful.
However when I load my project it says it is not registered.

I seem to remember I read about this ages ago but can't find teh instructions via VB6.

Can anyone help?

Thanks.

[HansV]

Try the following:
- Create a text file using Notepad (or any text editor).
- Enter the following line:

regsvr32 C:\Windows\SysWOW64\mscomctl.ocx

- Save the text file as a .bat file, or save it as a .txt file, then change the extension to .bat.
- Right-click the .bat file and select "Run as Administrator" from the context menu.
- Confirm that you want to run it.

Does that help?

[D Willett]

It ran ok from the bat file, but the same problem in VB6 although I think I've cracked it through the project references [browse]. There are a few other controls that need registering so this is going to take some time.

Thanks Hans

[HansV]

I hope you'll get it to work. The VB6 controls should still work on Windows 7 (and Windows 8/8.1), even the 64-bit versions.

[D Willett]

Hi Hans

I'm sure they will. I'll have to trawl through the log files to see which ones are causing the issue.
Not to worry :-)

Kind Regards

[D Willett]

Well I've had a couple of days nightmare with the upgrade.
I have successfully re-registered comm controls etc and they are working.
One control I cannot make to work is Richtxt32.ocx

From Administrator-cmd etc the file registers ok but will not register in the vb6 project.
If I try to add it as a component I get "name conflicts with existing module".

I'm really stuck on this and could do with some help................

[EDITED] All working now..
After downloading several fixes from Microsoft, dergistering and reregistering controls this now works.
Had to create a new project and add the Rich control into there first after editing the vbp file.

What a pain ...................................

Regards

Cheers

[HansV]

Try the following:
- Open your project file (the .vbp) in Notepad.
- If you see a reference to Richtxt32.ocx, remove it.
- Close and save the file.
- Open your project in VB6 and try to add Richtxt32.ocx again.

[D Willett]

Cheers Hans.
I edited my post above to show how I had fixed it using the same method.
What confuses me is I had already edited the vbp several times without avail.
It was only when I created a new project and edited the new vbp it worked... strange!!

I'm glad its now fixed --- phew !!!

[HansV]

Glad too!

[D Willett]

The saga continues....

After compiling successfully a new exe and distributing it out to the xp company users, the users are getting error 339 on the COMCTL32.ocx.
So I thought to recreate the setup package using Package and deploy. Reinstalled and still the same issue.
So I'm thinking this is because the xp users don't have a sysWOW64 folder.
The same occurs with 7 users also and the only pc which doesn't have the problem is mine where the compile is created!

Any thoughts on this??

I've included the vbp below in case anyone has any thoughts:

Code: Select all

Type=Exe
Reference=*\G{00020430-0000-0000-C000-000000000046}#2.0#0#C:\Windows\SysWOW64\stdole2.tlb#OLE Automation
Reference=*\G{420B2830-E718-11CF-893D-00A0C9054228}#1.0#0#C:\Windows\SysWOW64\scrrun.dll#Microsoft Scripting Runtime
Reference=*\G{F935DC20-1CF0-11D0-ADB9-00C04FD58A0B}#1.0#0#C:\Windows\SysWOW64\wshom.ocx#Windows Script Host Object Model
Reference=*\G{6B263850-900B-11D0-9484-00A0C91110ED}#1.0#0#C:\Windows\SysWow64\MSSTDFMT.DLL#Microsoft Data Formatting Object Library 6.0 (SP4)
Reference=*\G{00000205-0000-0010-8000-00AA006D2EA4}#2.5#0#C:\Program Files (x86)\Common Files\System\ado\msado25.tlb#Microsoft ActiveX Data Objects 2.5 Library
Reference=*\G{00062FFF-0000-0000-C000-000000000046}#9.2#0#C:\Program Files\Microsoft Office 15\Root\Office15\MSOUTL.OLB#Microsoft Outlook 11.0 Object Library
Reference=*\G{56BF9020-7A2F-11D0-9482-00A0C91110ED}#1.0#0#C:\Windows\SysWow64\MSBIND.DLL#Microsoft Data Binding Collection VB 6.0 (SP4)
Reference=*\G{94A0E92D-43C0-494E-AC29-FD45948A5221}#1.0#0#C:\Windows\System32\wiaaut.dll#Microsoft Windows Image Acquisition Library v2.0
Object={EAB22AC0-30C1-11CF-A7EB-0000C05BAE0B}#1.1#0; ieframe.dll
Reference=*\G{F5078F18-C551-11D3-89B9-0000F81FE221}#6.0#0#C:\Windows\System32\msxml6.dll#Microsoft XML, v6.0
Reference=*\G{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}#2.0#0#c:\Windows\SysWOW64\mscomctl.ocx#Microsoft Windows Common Controls 6.0 (SP6)
Object={F9043C88-F6F2-101A-A3C9-08002B2F49FB}#1.2#0; comdlg32.ocx
Object={20C62CAE-15DA-101B-B9A8-444553540000}#1.1#0; MSMAPI32.OCX
Object={48E59290-9880-11CF-9754-00AA00C00908}#1.0#0; Msinet.ocx
Object={935C9182-411B-4FFB-9512-97C8745743BC}#2.5#0; AResize.ocx
Object={6B7E6392-850A-101B-AFC0-4210102A8DA7}#1.3#0; COMCTL32.OCX
Form=frmSplash.frm
Form=frmImport.frm
Form=frmArchive.frm
Module=modJPG; modJPG-Comment.bas
Module=modStart; Start.bas
Class=cPOPupMenu; cPOPupMenu.cls
Form=frmLogin.frm
Form=frmViewArch.frm
Form=frmPrintMain.frm
Form=frmZoom.frm
Module=modWriteToLog; modWriteToLog.bas
Form=frmEntries.frm
Form=frmLoginEntries.frm
Class=clsCalendar; Calendar.cls
Class=clsDayInfo; DayInfo.cls
Class=clsDayInfoCol; DayInfoCol.cls
Form=DropDownCalendar.frm
Module=modScrollFix; modScrollFix.bas
Form=frmMenu1024.frm
Form=frmUnArch1024.frm
Module=modUtils; modUtils.bas
Form=frmWordDoc.frm
Form=frmWait.frm
Form=frmOrder.frm
Form=frmDisclaimer.frm
Form=PostCode.frm
Module=modPrintPdf; modPrintPDF.bas
Module=modTempSW; modTempSW.bas
Form=frmMethod.frm
Form=frmFTP1024.frm
Module=FormControl; FormControl.bas
Form=frmMerge.frm
Form=frmMain.frm
Form=frmColor.frm
Form=frmControls.frm
Form=frmFonts.frm
Form=frmFontStyle.frm
Form=frmPaint.frm
Form=frmSelector.frm
Module=DialogAPI; DialogAPI.bas
Module=SimplePaints; SimplePaints.bas
Form=frmShopwatchUtilities.frm
UserControl=InactiveTimer.ctl
Form=frmMap.frm
Module=modThumbView; modThumbView.bas
Form=frmFtpAll.frm
Class=FTPClass; FTPClass.cls
Class=FTPFileClass; FTPFileClass.cls
Form=frmDocImport.frm
Form=frmHistory.frm
Form=frmQuickMethods.frm
Form=frmSaveMethod.frm
Form=frmMenu.frm
Form=frmChangeAll.frm
Form=frmMMDocs.frm
Form=frmRotate.frm
Form=frmPASDocImport.frm
Class=ClsQrCode; ClsQrCode.cls
Form=frmQR.frm
Module=modQRPrint; modQRPrint.bas
Module=modNotDefPrnt; modNotDefPrnt.bas
Module=modRotate; modRotate.bas
Module=Module1; modFavourites.bas
Module=modIE; modIE.bas
Form=Form1024Image.frm
Object={3B7C8863-D78F-101B-B9B5-04021C009402}#1.2#0; Richtx32.ocx
Object={859DE455-7B89-457A-9743-C1081A14D235}#7.0#0; SuperPicture.ocx
IconForm="frmSplash"
Startup="Sub Main"
HelpFile=""
Title="MIC Office"
ExeName32="MIC-Office2.exe"
Path32="C:\Users\Dave.willett\Desktop"
Command32="MICOffice.exe"
Name="MIC_Office"
HelpContextID="0"
CompatibleMode="0"
MajorVer=2
MinorVer=0
RevisionVer=558
AutoIncrementVer=1
ServerSupportFiles=0
VersionCompanyName=".."
CompilationType=0
OptimizationType=0
FavorPentiumPro(tm)=0
CodeViewDebugInfo=0
NoAliasing=0
BoundsCheck=0
OverflowCheck=0
FlPointCheck=0
FDIVCheck=0
UnroundedFP=0
StartMode=0
Unattended=0
Retained=0
ThreadPerObject=0
MaxNumberOfThreads=1
DebugStartupOption=0

[MS Transaction Server]
AutoRefresh=1

[Jan Karel Pieterse]

To avoid havoc like this I would install some virtual computer software like the (free) Microsoft Virtual PC and add a virtual machine in there with a Windows XP and VB6 installation.

[D Willett]

Hi Jan
Long time no speak.
Thanks, Yes it seems I may have to do that as I see future problems from other software I manage here.
I've contacted our IT and asked them to set this up.

Kind Regards