After a year of working to provide market research for VA's emerging Fileman Evolution projects - especially after OSEHRA's December sprint to upgrade MSC Fileman 22.2 in support of VA's test-plan contract with Leidos, and the January VISTA Community Meeting in Sacramento - my health finally collapsed for six weeks of February and March. I returned to the office just in time to watch VA's next Fileman 22.2E testing contract sail over the plate before I could respond to it, much to my dismay and disappointment. But before I could grieve properly for missing one of the opportunities I had been awaiting for sixteen years, things began to heat up with VA's Fileman 23 initiative, due out as an RFP later this month. Of the two, this is the one the Fileman Team is most needed for, so we're deep into the analysis phase now, including the delivery of a serious of Future of Fileman presentations about the risks and rewards associated with it, to help the VISTA community align strategically around what needs to happen for this critical VISTA Evolution initiative to succeed.
Meanwhile, yesteday morning marked the renewal of our 5:00 a.m. classes with EHS of Jordan's FLAP team, where we resumed work on patch 1 for MSC Fileman 22.2, which extends %DT and %DTC to support the ISO 8601 international standards for dates and times, widely used on the Internet, and used now on the new, clean first lines for all of MSC Fileman 22.2's routines, as of early February when I completed my cleanup of MSC Fileman 22.2 for compliance with VA's VISTA programming Standards and Conventions.
Starting next week, I'll be resuming the final stages of the bundling of MSC Fileman 22.2, which will also include the fix of a bug I found that goes back over a decade.