Microsoft Office version: Difference between revisions

(12 intermediate revisions by the same user not shown)

Line 1:

~~[[CCMDB.accdb]]~~ uses ~~a mix of~~ MS Access ~~2010 and~~ 2019. ~~Upgrading any part of MS Office can break functionality, so we need~~ to ~~test first whenever there might be an upgrade~~.

Our project uses MS Access 2019 64-bit. We are doing

[[O365 Testing]] in preparation for moving to a new version.

~~== Shared Health project to upgrade to MS Office 2019 ==~~

See [[Finding your version of MS Access]] to find out what version you have.

See [[~~Upgrading from Office/~~Access ~~2010 to 2019~~]] ~~for instructions how~~ to ~~update~~.

As of ~~2021-04~~ there is a ~~project~~ to ~~upgrade all remaining workstations using older versions of~~ office to Office ~~2019~~. ~~We are working with '''Ryan Garcia'''~~ from the ~~upgrade~~ project ~~team~~ to ~~move our dbs over~~ to ~~2019. As of 2021~~-06-29~~, all collector laptops should now~~ be ~~updated and we~~ are ~~testing the main office programs.~~

Upgrading any part of MS Office can break functionality, so we need to test first whenever there might be an upgrade.

Specifically, Digital Health is upgrading our ancient Exchange (email) server from on-premise to cloud over the next few weeks, which requires modern auth and should be tested with our email automation. Also, we have a system of VBS, batch, VBA and possibly PowerShell scripts to run the beast, so we need to know things will work in the new setup.

== Verified Version==

* TT 2025-08-07: Microsoft Access 2019 MSO (16.0.10417.20030) 64-bit

== Version lifecycle ==

* [https://docs.microsoft.com/en-us/lifecycle/products/microsoft-office-2019 Office 2019] support ends

** initially support was supposed to end 2023-10-10

** extended support was added up to 2025-10-14;

** [https://learn.microsoft.com/en-us/office/ltsc/2021/ Office LTSC 2021] might be an option but [https://learn.microsoft.com/en-us/lifecycle/products/office-ltsc-2021 support also ends 2026-10-13] so this would only buy us 1 year

== Log ==

* 2025-08-13 - secured a laptop to do [[O365 Testing]]

* 2025-08-12 - received group email from Digital Health ICT Services that distribution list will be frozen in prep for Exchange migration - first general notification

* 2025-07-29 - teams chat from the Digital Health contact, still no project to replace O2019, but offered to get me licensed to install MS365 to test

* 2025-07-16 – email to Service Desk; got Request# REQ510946

* 2025-04-29 – emailed for follow-up; contact has no news and expects it will be a while since there really is no project just the idea of a plan…

* 2025-04-10 – emailed a Digital Health contact to see if there are plans for MS Office replacement

== Related articles ==

Line 10:

Line 29:

[[Category:IT Instructions]]

[[Category:MS Office]]

@@ Line 1: / Line 1: @@
-[[CCMDB.accdb]] uses a mix of MS Access 2010 and 2019. Upgrading any part of MS Office can break functionality, so we need to test first whenever there might be an upgrade.
+Our project uses MS Access 2019 64-bit. We are doing
+[[O365 Testing]] in preparation for moving to a new version.
-== Shared Health project to upgrade to MS Office 2019 ==
+See [[Finding your version of MS Access]] to find out what version you have.
-See [[Upgrading from Office/Access 2010 to 2019]] for instructions how to update.
-As of 2021-04 there is a project to upgrade all remaining workstations using older versions of office to Office 2019. We are working with '''Ryan Garcia'''  from the upgrade project team to move our dbs over to 2019. As of 2021-06-29, all collector laptops should now be updated and we are testing the main office programs.
+Upgrading any part of MS Office can break functionality, so we need to test first whenever there might be an upgrade.
+Specifically, Digital Health is upgrading our ancient Exchange (email) server from on-premise to cloud over the next few weeks, which requires modern auth and should be tested with our email automation. Also, we have a system of VBS, batch, VBA and possibly PowerShell scripts to run the beast, so we need to know things will work in the new setup.
+== Verified Version==
+* TT 2025-08-07: Microsoft Access 2019 MSO (16.0.10417.20030) 64-bit
+== Version lifecycle ==
+* [https://docs.microsoft.com/en-us/lifecycle/products/microsoft-office-2019 Office 2019] support ends
+** initially support was supposed to end 2023-10-10
+** extended support was added up to 2025-10-14;
+** [https://learn.microsoft.com/en-us/office/ltsc/2021/ Office LTSC 2021] might be an option but [https://learn.microsoft.com/en-us/lifecycle/products/office-ltsc-2021 support also ends 2026-10-13] so this would only buy us 1 year
+== Log ==
+* 2025-08-13 - secured a laptop to do [[O365 Testing]]
+* 2025-08-12 - received group email from Digital Health ICT Services that distribution list will be frozen in prep for Exchange migration - first general notification
+* 2025-07-29 - teams chat from the Digital Health contact, still no project to replace O2019, but offered to get me licensed to install MS365 to test
+* 2025-07-16 – email to Service Desk; got  Request# REQ510946
+* 2025-04-29 – emailed for follow-up; contact has no news and expects it will be a while since there really is no project just the idea of a plan…
+* 2025-04-10 – emailed a Digital Health contact to see if there are plans for MS Office replacement
 == Related articles ==
@@ Line 10: / Line 29: @@
 [[Category:IT Instructions]]
+[[Category:MS Office]]