Sorry, Petec, unfortunately, RCU committed not one, but three cardinal sins in the IT world when they did this. First, they did not test it properly before they implemented it, then they did not properly test their "fix" before telling us what we were supposed to do (and then tried to make it sound like it was our fault), and the biggest sin of all, they did not announce the change BEFORE they did it so that we knew what to expect. I dealt with IT on a daily basis, and I had to sit on them constantly until they "got it" in terms of proper testing before feature rollout and customer communication; they got REAL tired of coming to my office and explaining why no one could get anything done because they had made a "minor change" to our system.

This was not a security fix that had to be done in a hurry, this was a new feature that should and could have been tested properly and announced properly. After the fiasco here last year when the whole site changed without announcement, and they had to abandon the changes 24 hours later because NOTHING worked right, I would have thought RCU would have learned their lesson. A "minor bug" to an IT person can be a major hassle to a customer. Remember, RCU is a business and they make money by us being here and looking at and buying things from their vendors; if they PO customers enough, we can go elsewhere.

Jon