Mscomct2.ocx Can't register win 8.1 - vba

I have windows embedded 8.1 Industry Pro (64bit) and office 2010. I did everything that I was supposed to do ;
Just extract the .ocx file from the .cab file and Copy to the system folder c:\windows\sysWOW64 for 64 bit systems
Use regsvr32 through the command prompt admin to register the file "regsvr32 c:\windows\sysWOW64\mscomct2.ocx"
But when I go to additional controls, there's no "microsoft date and time picker."
What can I do ?
Thanks

After 2 hardworking days finally I found my problem. My problem was office64 bit edition not supports every activex like mscomct2.ocx when I installed office32 bit problem solved.

Related

ListView Common Control (mscomctl.ocx) not installed under Excel 2016 / Windows10

I'm using Windows 10 and Excel 2016 and I tried to install the Windows Common Controls (SP6) using the file mscomctl.ocx. It ran perfectly under Excel 2013 but not under Excel 2016. I'm looking for the ListView control which does no longer run on the new machine.
I performed the following steps:
Copy the mscomctl.ocx file from a running Windows 10 / Excel 2013 into the folder C:\Windows\SysWow64
Register the file with the cmd prompt regsvr32 C:\Windows\SysWow64\mscomctl.ocx
Referenced the mscomctl.ocx in VBA which then appeared in the list with a checked box
Checked the registry and theres only an entry for Version 2.2. Altough on the running machine I've got 2 entries: (Standard) & PrimaryInteropAssemblyName) where on the not running machine there's only the (Standard) entry.
Step No. 5 would have been adding the control to the Standard controls but None of the common controls does appear in the list.
Does anybody have experienced similar issues? If yes, could you resolve them?
Many thanks
Adrian
This is happening because mscomctl.ocx is a 32 bit only item. It will not work in 64 bit mode.
Addendum: in July 2017 Microsoft published a 64-bit version of mscomctl.ocx, thus since then it is possible to use its controls from Office 64-bit. The 64-bit version of mscomctl.ocx is also part of newer Office versions (like Office16). A good article about using mscomctl.ocx with Office 64-bit is available here.
Instead of coping the file from somewhere, you could always download them from Microsoft
Make sure the "Microsoft Windows Common Controls 6.0 (SP6)" reference does point on the SysWoW64 folder. If not Use the "Browse" button to select it.
Left click on the "Toolbox" -> "Additional Controls", make sure the "Selected Items Only" is not checked, and look for the "Microsoft ... 6.0 (SP6)" controls.
Note that you might experience issues when trying to open the resultant workbook in older versions of Windows and/or Excel.

Win8/VB6 can't find project or library for common functions (str, Space$)

I have installed VB6 on my Windows 8 64bit laptop, I installed SP6 and when I try to run projects that I had working on my windows 7 32bit laptop I am running into a problem with common functions like Space$ or Str, where it tells me "Can't find project or library".
After some googling I have tried copying over my comdlg32.dll from the windows 7 laptop over to the syswow64 folder on the win8 laptop but saw no change. I have installed SP4 after I read that would solve it but that didn't work either. I also read that msderun.dll would help but after dropping that in syswow64 I did not see any change either.
Does anyone know how to fix this on Windows 8?
Find msvbrun60.dll (in 32 bit windows type regsvr32 msvbvm60.dll, for 64 bit do the same with c:\windows\syswow64\regsvr32 msvbrun60.dll). All those functions are in vba library which is msvbvm60.dll. If that fails reinstall the runtime files http://support.microsoft.com/kb/290887.

Installing simplest plugin on German Windows XP

I'm trying to figure out why the simplest firebreath plugin wont install on a German Windows XP SP3. I'm running Windows XP as a virtual machine.
The event viewer in Windows XP tells me something about the Windows Installer aborting but not why. I'm logged in as the administrator.
The installer works on Windows 7.
For development I use Windows 7, Visual Studio 2010 and some one months old firebreath trunk.
Is this is known problem? What are the typical steps I could use to track down the issue?
Regards,
Christian
If you get an error saying module can't be found it means that you are missing a .dll file needed to make the plugin work. The most common if it works on most computers (or many) but not that one is that your .dll was compiled with a dynamic runtime, in which case you'll have to install the common runtime for whatever version of visual studio you compiled it with.
For example, the runtime distributable for vs2008 is at http://www.microsoft.com/en-us/download/details.aspx?id=29
Dependency Walker might help you to find out which dll is missing.

Griaule biometrics DLL control did not work in 64 bit O.S

We purchase a licensed Control for Biometric from Griaule biometrics.
we are using this Control on a Window Application's form.The AxInterop.GrFingerXLib Dll control is working fine on the 32 bit operating System.
But due to some reason we change the Operating system from 32 bi**t to **64 bit.
On the 64 bit operating system the window form on which we are using the AxInterop.GrFingerXLib DLL Control is unable to Create.
And if we remove the Control from the Form working fine.
We use the the latest release of Fingerprint SDK 2009 but it still not working.
We also did that we remove the Control from the form and then again include the control on the form then it gives some ActiveX control not find related Error.
We are using Visual Studio 2008 and Windows Server 2008 64 bit operating System.
Its urgent issue and we want to resolve it as soon as possible.
Please provide a needful support.
I Have Found The Solution
When I build the .EXE with x86 Configuration the Problem have been resolved
Steps i Followed
Build-->Configuration Manages
Here set the application's target platform. to x86
Build the Project
u will find a Newly created Folder x86 under Bin Directory
use this Exe in 64 bit Machine it will work fine!

How do I resolve "Run-time error '429': ActiveX component can't create object"?

My company has a VB6 application using Crystal Reports 7 which a client has asked to be installed on Windows 7 32 bit. It is currently installed on Windows XP 32bit SP2 machines at the client. Connection to the DB is done via ODBC to SQL Server 2000 instance on another server.
On Windows 7, the installation works fine, however when you try to open the application, the error is given.
I have looked at the following:
Registering all the dll's and ocx files using regsvr32. Some will not register as they either are registered already or the following message is given "Make sure that "[name].dll" is valid DLL or OCX file and then try again." I read this forum thread regarding this: http://social.msdn.microsoft.com/forums/en-US/vblanguage/thread/0653f685-4526-45d9-89f3-8c479a6b4c62
Monitored the opening of the application using a ProcessMonitor application to try and spot if there is a missing dll or ocx file - this does not seem to be the case.
Reviewed the application according to this list and nothing seems to be against these guidelines
I've noticed two items in the knowledge base that relate to this
http://support.microsoft.com/kb/281848 - the comdlg32.ocx bundled with the application is version 6.0.81.69 and the one in the system32 folder on the dev machine (WinXP 32 bit) is 6.1.97.82. However if this was the issue then surely it would not work currently?
http://support.microsoft.com/kb/184898 - I'm not sure how to confirm that this is the issue
Finally, due to complexities, I am not allowed to make code changes to this application. Even if I was, I'm not a VB6 programmer, just the guy who got the terribly support project! If code changes are required, then I'll have to investigate using WinXP mode.
Update: I get the same error in XP Mode. That's a Win XP with SP3 VM. This runs on a Win XP SP2 VM, is there potentially something in SP3 that would have caused this to occur? Or is it just a fact of it being XP Mode?
I got the same error but I solved by using regsvr32.exe in C:\Windows\SysWOW64.
Because we use x64 system. So if your machine is also x64, the ocx/dll must registered also with regsvr32 x64 version
The file msrdo20.dll is missing from the installation.
According to the Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008 and Windows 7 this file should be distributed with the application.
I'm not sure why it isn't, but my solution is to place the file somewhere on the machine, and register it using regsvr32 in the command line, eg:
regsvr32 c:\windows\system32\msrdo20.dll
In an ideal world you would package this up with the redistributable.
This download fixed my VB6 EXE and Access 2016 (using ACEDAO.DLL) run-time error 429. Took me 2 long days to get it resolved because there are so many causes of 429.
http://www.microsoft.com/en-ca/download/details.aspx?id=13255
QUOTE from link:
"This download will install a set of components that can be used to facilitate transfer of data between 2010 Microsoft Office System files and non-Microsoft Office applications"
You say it works once you install the VB6 IDE so the problem is likely to be that the components you are trying to use depend on the VB6 runtime being installed.
The VB6 runtime isn't installed on Windows by default.
Installing the IDE is one way to get the runtime. For non-developer machines, a "redistributable" installer package from Microsoft should be used instead.
Here is one VB6 runtime installer from Microsoft. I'm not sure if it will be the right version for your components:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7b9ba261-7a9c-43e7-9117-f673077ffb3c