Open In 32-bit Mode
To always open an application in 32-bit mode: Open the Application Wizard pane in System Preferences and click Applications. Click the Add (+) button at the bottom of the list, browse and select the application, and click Add. Select the ”Open in 32-bit mode” option. When launched from the Open menu the application will always run in 32-bit mode.
First, let me make clear what I'm saying. Usually an ACCDE is created to protect the design of forms, reports, and VBA codein a database application. First, let me make clear what I'm saying. Usually an ACCDE is created to protect the design of forms, reports, and VBA codein a database application. It not clear at all what is not working for you.You can’t use an x32 bit accDE appcation with the x64 bit version.However, you CAN create blank new database, and import the tables (data).
If the accDE file in question ONLY has some data you wish to work with, then this may well work well for you.However, if you need to use the forms, reports, and the application someone has created in Access, then you have a VERY different problem to solve.The possible solutions are:Use an accDB as opposed to an accDE. An accDB can be opened and used with both x32 and x64 bit office. However, if the application is complex, and the x32 bit version used x32 bit features, then you have to work with the original developer of the applicationand have them modify their code to work for both x32 and x64 bit versions of Access/office.How to fix and deal with this issue is outlined here:Another possible work around is to install the access 2010 x64 bit runtime on that computer. This will allow the user to launch + use the Application as x32 even with your current x64 bit version of office.So, it not at all clear what is not working but it REALLY comes down to what you attempted, and what will work for you.As noted, perhaps you just need to look at the tables and view the data. If this is acceptable, then creating a blank new database (which will default to x64 bits), and THEN you simply import the data (tables) into this new accDB file. However, thiswill ONLY get you the tables.
The forms, reports, code and the rest of the application can NOT be copied over this way.So, best approach is to use an accDB. If you must use an accDE, then you have to go back to the original creator of the database, and have them create an x64 bit version of the accDE for you.So, you can use + see + view the data by importing, but if you need the application parts such as forms, reports, code etc., then you MUST go back to the original accDB used to create the accDE and produce a x64 bit version of the accDE forthis to work. (In most cases you can just open + use the accDB).So, using an accDB is the starting point for this solution.As noted, because the above can be a real hassle and a lot of work, then consider the idea of installing a x32 bit version of the Access 2010 runtime – as that is also a workaround but a far less painful workaround if you don’t’ have the time, thepeople and the expertise available to create a x64 bit version of the accDE.So this will come down to your ability to talk to, and deal with, and work with the person who created the accDE for you. Perhaps that person is sitting next to you – so not a big deal or problem.However, if that person is not available, or does not have the skill set to create the x64 bit version of the accDE for you, then installing an x32 bit version of the Access runtime is far less work and painful then working on the accDB to make itcompatible with both x32 and x64.Note that AFTER the accDB is made to work with both x32, and x64, if you ARE still wanting to use an x64 bit version of the accDE, then you MUST compile (make) the accDE x64 bit version with an x64 bit version of Access. So while the accDB can be madeto work with both x32 and x64, the resulting accDE MUST ALWAYS be created with the same bit size version (x32 or x64) that matches the SAME x32 or x64 bit version the user is working with.So which solution works best for you will depend on the availability of the person who created the accDE in the first place. If that person is available, then you can give that person the included link for information on how to make their accDB workfor both x32 and x64 versions of Access.Regards,Albert D. Kallal (Access MVP 2003-2017)Edmonton, Alberta Canada.
How technical an answer do you want? You can probably force the exe to always run 32bit with a few SDK tools, but it does require a little work.The easy answer is to launch from a 32bit process (eg.
Use%SystemRoot%SYSWOW64cmd.exe to launch).The more complex is to check what kind of exe it is, then modify it yourself. Background here is to understand that compiled code from languages that directly work with the Windows APIs are created as 32bit or 64bit at compile time by the developer. This cannot then be changed without going back to the source code.However increasingly applications are written via a virtualisation layer that makes writing applications easier. There are two common ones:.NET and Java. I'm not sure about Java except knowing that forcing the right Java runtime install with solve the problem.For.NET you can use SDK tools to:. Validate that the application is 'AnyCPU': corflags myExe.exe. Using a utility from the.NET SDK to read the headers of a.NET assembly, for an exe will return something like:Version: v4.0.30319CLR Header: 2.5PE: PE32CorFlags: 0x20003ILONLY: 132BITREQ: 032BITPREF: 1Signed: 0the 32BITREQ tells me this is AnyCPU because 32bit is not required.
Open Firefox In 32 Bit Mode
Use corflags with its /32BITREQ+ option to modify the exe to be 32bit only.