From now on we are running OCX-Files and some Add-Ins in 32 bit MS Access, planned would have been a changeover on 64 bit, i already tested different ways of register the ocx in the syswow64 folder and so on, but it seems Ms Access is not recognising the 32 bit control elements.
Is there a way to run them on the 64 bit MS Access?
You can't. For 64-bit Office you need 64-bit controls / COM Add-ins.
See Choose between the 64-bit or 32-bit version of Office :
Reasons to choose the 32-bit version
You have 32-bit COM Add-ins with no 64-bit alternative. You can continue to run 32-bit COM add-ins in 32-bit Office on 64-bit Windows. You can also try contacting the COM Add-in vendor and requesting a 64-bit version.
You use 32-bit controls with no 64-bit alternative. You can continue to run 32-bit controls in 32-bit Office like Microsoft Windows Common Controls (Mscomctl.ocx, comctl.ocx), or any existing 3rd-party 32-bit controls.
Related
My Softwares:
Python 3.4 -64 bit
PyODBC 64 bit
MS office package Installed (32 bit)
Problem:
Now, I try to access MS Access 2010 installed in my computer using PYODBC. It does not work regardless of what I try. My error is always this:
pyodbc.Error: ('IM002', '[IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified (0) (SQLDriverConnect)')
I already looked at:
pyodbc and ms access 2010 connection error
Cannot connect to Access DB using pyodbc
It is suggested that it is 32-64 bit problem which I am sure it is. Is there some modification that can be done to make it work without installing 32 bit python and 32 bit pyodbc? I checked this website.Using ODBC (32-bit and 64-bit) on 64-bit Windows which explains about accessing the control panel to modify ODBC connnection and/or drivers. However, I don't know much about windows database connection internals to commence some changes.
Is there something that I can do to make it work?
Is there some modification that can be done to make it work without installing 32 bit python and 32 bit pyodbc?
Not really. If you have 32-bit Office installed then you have the 32-bit version of the Access Database Engine (a.k.a. "ACE"), and only 32-bit applications can use it.
The installer for the 64-bit version of the Access Database Engine will abort if it detects 32-bit Office components. There is a way to force the installer to continue, but that is not recommended because it can apparently break Office.
Bottom Line: The "bitness" of your application must match the "bitness" of the installed Access Database Engine. So, practically speaking, your options are
Use 32-bit Python and pyodbc, or
replace your 32-bit Office with the 64-bit version.
My development computer has Installed 32-bit Access (Office 365). I now have users with 64-bit Access who cannot open the application. Is there any way to install 64-bit (either Runtime or full) for debugging purposes? So frustrating!
You have to convert your application to 64bit Access
This is done by obtaining a Ms Access 64bit (Office) ..opening your application on it and working out any bitness differences.. and of course providing the appropriate driver for MySQL : https://cdn.mysql.com//Downloads/Connector-ODBC/5.3/mysql-connector-odbc-5.3.14-winx64.msi
In my manifest xml file I have this setting, does it mean that only 64bit Windows10 installations do accept my package? My app is native 32bit, which setting is recommended to this field to make it work with both 32 and 64 bit os?
ProcessorArchitecture="x64"
I think if you set ProcessorArchitecture="x64" in your manifest xml file, the package just only was installed on the x64 Windows 10. But you can set
ProcessorArchitecture="x86" in the manifest, because this x86 package can all work fine on x86 and x64 Windows 10.
This answer based on VS C++, but the context is basically the same for manifests. Surprised to see that W10 X86 only installations actually exist, but they do, (or did), because, as the free W10 upgrade did not provide an option to change architectures, only a clean install would.
However, from an old Tom's Hardware post:
All processors since the Opteron in 2003 and the intel Pentium 4 Prescott ( the latter editions ) has 64bit instruction set and will all run 64bit windows.
Thus as long a MSFT continues to support 32 bit architecture, X86 is the safer option, although X64 would probably still work.
processorArchitecture='*'
covers all bases as well.
Microsoft's documentation says to use processorArchitecture="ia64" for Windows 64-bit builds; however, they do not follow their own advice. Microsoft uses "amd64" for 64-bit builds of WordPad.exe and iexplore.exe (Internet Explorer 64-bit) according to the embedded app manifest of these EXEs on my Windows 10 computer.
The wxPython package must run in 32 bit mode, but the official MySql download page does not have any link to download the 32bit installer. Do you know where to download the 32bit installer of MySql?
Thanks
UPDATE: I am trying to download MySql 32 bit for Mac.
You are incorrect. The Cocoa build of wxPython supports both 32-bit and 64-bit architectures. From the wxPython downloads page:
The file with "cocoa" in the name use the Cocoa API for implementing the GUI, requires at least OSX 10.5, and supports either 32-bit or 64-bit architectures.
The Carbon builds are built for i386 and PPC.
Also note that if you go into the Development Releases tab on the MySQL downloads page, it has 32-bit tars and dmgs
I'm building an SSIS package on Microsoft Visual Studio Ultimate 2012 Trial Version to import an access database, but I can't see the correct provider (Microsoft Office 12.0 Access Database Engine OLE DB Provider) from the drop down when creating the connection string. I downloaded the AccessDatabaseEngine_x64 since the installed MS Office is a 64bit, I still can't see this provider that I'm looking for. I'm building this SSIS package on a Windows Server 2012 64 bit machine.
I need to know what I should do to be able to see this provider.
Can somebody help.
OK. this is mostly assumption but holds true for database drivers. I will quickly be downvoted if this is incorrect.
I assume your version of Microsoft Visual Studio Ultimate 2012 is a 32 bit app, so you cannot see 64 bit drivers.
Regardless of what type of install of Office you have, it will create an output file, and that file does not have 'bitness' - i.e. the same file is produced regardless of whether your office app is 32 bit or 64 bit.
You just need to match your SSIS runtime with your driver. So if your SSIS package will be running in 64 bit, you need a 64 bit driver to access an Office file.
If it will be running in 32 bit you need a 32 bit driver.
Normally you just install both versions, develop in 32 bit and run in 64 or 32 bit.