:: Copy this cmd script to a folder including these MS Office files: Here is a sample CMD script that demonstrates the workaround: :: GetOfficeVer.cmd - Print the version of a licensed MS Office package. Is there an alternate way to programmatically distinguish Office 2016 from Office 2019?Ī workaround is to parse the version number from output of the MS Office Client Software License Management Tool, OSPP.VBS, run with the /dstatus option. That is just not right! The 20 feature sets are clearly distinct, so they should not be lumped together: Recently, though, I was surprised to find that it also reports 16.0 for Office 2019. Since then, it reports 15.0 for Office 2013, and 16.0 for Office 2016.
The diagnostic faithfully reports MS Office versions consistent with the post from 2011. Wscript.Echo "Excel Version: " & excelApp.Version Set excelApp = CreateObject("Excel.Application") Here is a VB Script that diagnoses which, if any, version of Excel is installed to the system: On Error Resume Next Doug Glancy directly addressed the question with VB code that prints the version property of Excel Application object: For instance, the number 14.0 corresponded to Office 2010. Mathieu's reply, the accepted answer, correlated numbers used to identify MS Office in the registry versus the product versions. Identifying Excel version programmatically
But now I find that it incorrectly reports MS Office 2019 applications as MS Office 2016.Įight years ago, M. It has worked correctly for MS Office versions 2003, 2007, 2010, 2013, and 2016. I maintain a diagnostic that programmatically determines the version of MS Office applications, including Excel and Word.
0 kommentar(er)
