O365 Testing

From CCMDB Wiki
Jump to navigation Jump to search

Support for our current Microsoft Office version is ending in Oct 2025 so we are testing O365 which will eventually replace it.

Plan

  • TT will do basic testing
  • then work with Michelle for data collector testing
  • work with Pagasa for testing of CFE


  • The laptop doesn't have SAS so we need to plan separately for testing this. Julie, what are your thoughts?
  • SMW


  • Cargo


  • Categories

Checklist

CCMDB

  • plain running our DB in the new version
    • ran no problem
  • any Macro security issues
    • test laptop is in collector OU so I guess whatever that does took care of this
  • importing Cognos
    • gave error because at least one field name has a trailing space;
  • VBA libraries we include and whether they will need to be brought to a new version
    • the references all still work, and AI thinks they will be around for the forseeable future, so leaving that alone
  • DB connectivity, we use VBA to reconnect front and back end and to send
    • we do every time, so this must work then...
  • Outlook email tie ins: email buttons and also the Cognos import
    • no problems generating email, no problems with email for importing cognos
  • Sending (LK tested)

CFE

  • VBA
  • only managed very preliminary testing before my test account to access O365 was shut down.

Other things we do in MS Office that we might want test?

  • Labs importer
  • any of our legacy data storage
  • any VBS/Powershell scripts that might interact programmatically. We used to have some, not sure if we still do.

Changes made for pasting into wiki change log

  • added Sub dump_all_VBA() to be able to back the changes up to git
  • added code to Sub import_new_Cognos to strip trailing blanks off field names
  • changed all OrderBy parameters to be bracketted


changes working on

current:

  • acCmdSaveRecord -> Dirty=false

queue:

  • ANSI wildcard
  • Date/time equality tricks using CSng In cb_tmpv2edit_Click
  • US-literal dates inside SQL strings - #12/31/2999# forced in by VBA but ambiguous
  • Event binding name drift for form_open

continue making list at Form_MouseWhee

Log

  • 2025-08-...
    • borrowed Test laptop from Tom for 1 month
    • Laptop was set up with W11 and O365 for testing

Related articles

Related articles: