Yup, It's back. Obviously some code that was already in the works when we had this "update" reversed six weeks ago has now been installed and the issue is back. I'm another user who's been actively operating one version or another of QuickBooks for 25 years and this is one of the most frustrating things they've ever done!