I just updated my MS Office 2016 to version 16.0.8067.2115 (which is the latest version if I'm correct).
I read here that the latest version supposedly has support for using SVG files.
However, I am unable to insert any svg file into any office program (using Insert > Picture from the ribbon or by dragging a file into an office program).
Am I doing something wrong? Does this version of Office not actually support SVG files? Or is there some setting that I missed?
I found the answer to my own question here: https://www.msoutlook.info/question/office-update-channels
Apparently, new updates like the ability to use SVG files are solely available for Office 365 subscribers and not for people who bought a one-time licence for Office 2016 (as I did).
Related
I have created an excel custom function in SharedRuntime. I have used JavaScript 1.1 version and SharedRuntime 1.1 version. My custom function is working fine in office 365, but it's not working in offices 2013, 2016, and 2019.
I don't know why this is happening. Can anyone tell me where I am doing a mistake.
The shared runtime may not be supported on older Office versions. You can check out the minimum Office versions in the Shared runtime requirement sets section.
I'm developing an application written in Visual Basic 6.0 that supports exporting listViews to Microsoft Excel documents. Everything works perfectly fine if a user has an older version of Microsoft Office installed.
Now I want to add support for users who only have Microsoft/Office 365 on their systems. I've googled my way into depression in the past couple of days because I don't know much (or anything really) about dll/ocx files or registries. I'm not even sure if something like this can even be done because VB6 is really old, as noted here.
I've tried using this approach, but it didn't help me.
Right now, I'm getting a 429 runtime error
ActiveX Component can't create object
on line
Set objExcel = CreateObject("Excel.Application")
I only have Microsoft 365 trial version (no older ones) installed on the system and have these two things checked in my references:
I've also tried searching for Excel.Application in the registry, as suggested here, but I can't find the path to the corresponding ActiveX file (which probably means it is not registered if I understand this correctly).
What can I do? Any help would be greatly appreciated.
Never mind, I found the answer myself. The problem was that I had older Office versions installed when I installed new 365 package and for some odd reason the .dll files for 365 version weren't registered. When I deleted those older versions all the working .dll files were gone with them.
I did a repair of the 365 installation and it's working perfectly now.
I'm developing an office-js addin for corporate client which insists on using legacy versions of Excel (1708 or 1808).
But when I install excel from office 365, I get version 1906.
In the old days, with software, there were installers you could find in a directory that had version stamps on them, and you could create a VM, and just install the version you wanted. But the fancier installers appear to download stuff automatically and always (at least default to) the latest versions.
How do I install a legacy version of Excel on a VM for testing?
There's no special process for getting an earlier version when you are testing add-ins. It should be the same process as an end user would use. Please try the steps at this article: Revert to an earlier version of Office. I think you can find the build numbers that you will need either from your customer or from this page: Update history of Office 365.
I'm working on a spreadsheet that I created on a different machine with an install of office 2016 version 1701. I'm running 2016 professional version 1707.
Many of the new functions won't work, for example Concat.
I've tried updating my install but it appears to have the most recent updates.
Any ideas why I wouldn't have access to the most recently released functions?
Those new functions are only available in subscription versions of Excel (i.e. you need an Office 365 subscription), and are not the 2016 versions. So if you want something equivalent, you've got to use a UDF. Here's a link to a Concat UDF I wrote some time back. You can also no doubt find equivalent UDFs for the other new features that aren't in your non-subscription version via Google.
I'm using Wix v3.0 (which boils down to an MSI installer) and I'm trying to author a condition to ensure that Excel 2003 is installed. What is the best (most robust) way to detect the presence of Excel 2003 on a machine?
I've seen lots of different suggestions, but no definitive or authoritative answer.
I found a file in the Office 2003 toolkit, Office 2003 Keypath and Default Installation Settings workbooks that contains all the GUIDs for the Components of Office. Based on this, I used a Component Search to locate the Core Excel component. In WiX my condition looks like this:
<Property Id="EXCEL2003INSTALLED">
<!-- This is the Component Id of Global_Excel_Core -->
<ComponentSearch Id="DetectExcel2003" Guid="{A2B280D4-20FB-4720-99F7-40C09FBCE10A}" Type="file"/>
</Property>
<Condition Message="This application requires Excel 2003 to be installed."><![CDATA[Installed OR EXCEL2003INSTALLED]]></Condition>
This page has Component Guids for other Office Apps and other versions.
We check the InstallRoot registry key at:
HKLM\Software\Microsoft\Office\12.0\Excel\InstallRoot
(Replace 12.0 with the relevant version number for your application).
Note that on 64-bit operating systems, this will be reflected to the 32-bit section of the registry (see this Microsoft article for more information on Registry Reflection).
This seems to work well for versions 2000, XP, 2003, 2007 and 2010 at least. The only change for 2010, is that the 64-bit version needs you to look in the 64-bit section of the registry.
you could try checking the registry, or perhaps the typical install path for excel.
Excel (Office) is also installed by windows installer.
Why are you not checking for the excel component codes?