Hello All, in my environment, there are different versions of ms office installed and i need to make an analysis which will show whether the office is 32 bit or 64 bit. Please help me to achieve this.
One option would be to look for a Microsoft Office product name in the Add Remove registry hives; x32 registry and x64 registry inspectors will allow you to look in the respective 32- and 64-bit hives to give a simple True/False for 32-bit versions, or, if you want to make it more complex, return the version installed. That way, you would have two properties, one for each architecture, returning either True/False or the version installed.
Knowing your version helps you choose compatible software add-ons and plugins. Plus, some features may vary between different architectures. So, being aware of your version makes for a smoother experience.
Fun fact: Microsoft Office 1.0, the first-ever office productivity suite, was only available as a 16-bit release for Windows! It included popular applications like Word, Excel, and PowerPoint which revolutionized document creation and data management.
Which version should you choose? If you work with complex files, large databases or memory-intensive tasks, go for the 64-bit version. It provides greater stability and capability to manage large data.
On the flip side, if you use Office mainly for basic activities like writing and creating presentations, the 32-bit version should suffice. It is also compatible with most add-ons and external programs.
To check your Microsoft Office version, utilize the following solutions: Using the File Options and Using the Control Panel. The File Options method allows you to access version information directly within the Office application, while the Control Panel method provides a system-wide view of all installed versions.
We are going to migrate to sap gui 7.40. Currently we have all our clients with SAPGUI 7.30 and 32-bit microsoft office. But now we do not know if already with 7.40 we could have 64-bit office. According to note 1442028 it is supported except If you use other components that interact with Microsoft Office (for example, Business Explorer or Interactive Excel), only the 32-bit versions of Microsoft Office can be used..
Before installing Office 64-bit, you have to know the advantages and disadvantages of using Office 64-bit with SAP GUI 740 as well as the terms of the license agreement you have with Microsoft regarding Office 64-bit, there may be an additional cost associated with which may prohibit the enterprise-wide deployment of Office 64-bit.
To streamline the installation process, we use the SAP GUI Installation Server to prepackage the SAP GUI and SAP BusinessObjects for Analysis and additional components to reduce the size of the installation package to a minimum.
To deploy the software package(s), we run a script on the user's pc's/laptop to verify which OS and Office version is installed which includes checking the 'bitness' indicator of Office and checking that certain prerequisites are met - then the script selects the appropriate package to deploy and apply the necessary configuration settings.
We are currently testing SAP BusinessObjects Analysis for Office 2.4 (32-bit and 64-bit) that was released earlier this week to determine if it is ready to deploy to our users for productive usage.
As to a SAP GUI 64-bit version, I doubt whether we will get a version as last I know in the communication from SAP a while ago (a long time ago) that to create a 64-bit version of the SAP GUI is extremely complex, and also looking at SAP's UX strategy it does seem unlikely it will happen.
What's the latest word on Sage 300 and Office integration? Today we are running Sage 300 2018 and we are currently limited to Office 2019 32-bit. We are upgrading to Sage 300 2021 this spring but it doesn't appear that Sage 300 2021 supports 64-bit Office. Is that right?
Has there been any discussion about supporting 64-bit Office? or any options for those companies that don't have a choice due to other requirements in their infrastructure? Maybe workarounds or optional configurations?
I was afraid you'd say that, although not surprised. As a systems admin, the default configuration is always the easiest to support and lately that has been 64-bit Windows + 64-bit Office. I'd just as soon maintain one base image with Windows/Office 64-bit.
On a side note, we have several 32-bit apps that seem to integrate fine with 64-bit Office. Adobe Acrobat, Mitel and Zoom come to mind. Tight Office integration between 32-bit apps and 64-bit Office. Seems doable with 32-bit Sage as well.
My understanding is the later versions of S300 works fine with x64 of Office and it comes down to more a matching of system privilege's between the two systems. Like you cant have S300 running with admin privilege's and office not or vice versa. Or even running as Admin in either may cause Office to spit the dummy.
Sage 300 is a 32 bit application, it will never talk to Office 64 bit. Not unless Sage 300 is rewritten in 64 bit, but that is not going to happen. With that said.... you can export/import data no matter which Office 32/64 bit you have installed, you just cannot run FR and some other integrations that require both applications to be 32 bit.
by the Sage 300 support team, who advised that MS Office doesn't have an option to mix and match 32bit apps with 64bit versions of apps.
The team also recently posted a blog for Sage 300 version 2022 (6.9) titled After upgrading Microsoft Excel to 64bit, Financial Reporter returns error with Excel Add-in. which gives steps on how to ensure a proper 64bit install of Microsoft Office. Hope this helps!
My question was specifically about Sage's support of the Office 365 version of Microsoft Office (as opposed to Office 2016 and Office 2019). To clarify, can you please ask the Sage 300 support team the following two questions?
I can confirm that on 2022 PU4, you can run 64-bit office, not only with Financial Reporter, but with custom VBA programming. We upgraded one of our big clients last week, and they're happy that 64-bit Excel finally runs.
The only issue I had was with VBA forms that had a Fieldedit control and a Datasource. The Datasource control is not currently available in 64-bit. The KISS solution for my client was to abandon the pretty finder and use a simple text field for them to type in the vendor number.
I was able to get the Financial reporter running but the Sage macros would not run. the VBA would not initiate or even give an error message when attempting to run any macro. Sage intelligence also did not run correctly and would not initiate running a report.
As a test we uninstalled the 64 bit Office and installed 32 bit office and everything ran correctly. This tells me that Sage 300 is NOT compatible with 64 bit office. It will not allow any out of the box macros run or any customer macros.
My old comments haven't aged well, because I know now that macros will run on 64-bit, we just converted our Acumen tools to run on either 32 or 64 bit. What doesn't work in 64-bit is data source controls on forms, so our nice finder forms got broken. We just replaced them with regular VBA list boxes. We use this to tell what version we're running:
03c5feb9e7