Ted I can easily, easily see how this happened to him. It just happened to me! The release notes for 7 said NOTHING of this, and the upgrade chart in SEP 12.1 documents stated the upgrade path covered 11.xxx
And isn't that was 7 is - 11.xxx?
Our issues is that Insight - the reseller, dropped the ball BIG time like they ALWAYS do, and so our license expired and I was not able to get 12, but was able to get the early documents - the stuff from the beta I had, etc. and read them end to end. Good, it would upgrade over 11.xxx it said.
I WAS able to get 7 so downloaded it because for some reason although our licensing is screwed up (thanks again to Insight and some lack of planning by some folks in our chains) it allowed me to get the latest 11, but not 12.
Besides, it's a WHOLE lot easier to upgrade a whole system to 11.0.7 from 6 than it is to go from 11 to 12, so 12 takes more planning, test servers, testing on clients, test databases, etc. - weeks of planning on a government environment. Where updating 11.x to 11.y takes only days if that even. I can push it out inside of a week, where 12 will be in a month even if I had it in hand.
So yeah, I see very easily how and why this happened to him - it happened to me, and I bet it's not all that uncommon!
Now I need to ask - knowing that 12.1 was out, why was 7 changed to the point that it excluded it from being in the upgrade path? Why did they make changes to 11.0.7 so that upgrades to 12 would no longre work knowing full well that the logical path would be weeks of testing, then moving to 12.1 but needing to keep 11 current in the mean-time?
I see a little loss of logic on this one, sorry - no offense to you.