Microsoft Office version: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 23: Line 23:
  | todo_action = 2025-08-07
  | todo_action = 2025-08-07
  | question =   
  | question =   
* I have been in contact with Shared Health about this; they are aware but don't have a project right now to update Office. Offered us to install the new version to test recently, but I have not had bandwidth. [[User:Ttenbergen|Ttenbergen]] 11:39, 7 August 2025 (CDT) }}
* Test new version...  }}


== Log ==
== Log ==
2025-08-13 - secured a laptop to do testing
* 2025-08-13 - secured a laptop to do 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-16 – email to Service Desk; got  Request# REQ510946
* 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-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-07-16 – email to Service Desk; got  Request# REQ510946
2025-04-10 – emailed a Shared Health contact to see if there are plans for MS Office replacement
* 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





Revision as of 20:53, 13 August 2025

Out project uses MS Access 2019 64-bit.

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

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

  • Test new version...
  • added: 2025-08-07
  • action: 2025-08-07
  • Cargo


  • Categories

Log

  • 2025-08-13 - secured a laptop to do 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

Related articles: