Brandon, remember that Microsoft is not run like a single company. It's run like a bunch of companies with the same name. Each group is a piranah, feeding off the others. Would I like to see something more concrete? Yes, but the truth is, EVERYTHING changes, not just MS.

Are web sites still just grey background with black text, using only HTML frames and tables?
Does anyone really use CGI for web sites?
Has Oracle made changes to their products?
Didn't the world's largest PC manufacturer just announce they are getting out of that business?
"This is not your father's Oldsmobile"... Oh, wait. Nevermind
How many updates to Google Chrome have you installed?
Where's CORBA?
Remember the Cadillac Catera?
What's this New Coke?
Have you ever heard of RC Cola? How about Like Cola?
Why can't I buy Snapple sodas anymore?
My favorite candy bar when I was a kid is no longer available. I don't even remember it's name. But it was fantastic. A layer of dark choolate, a layer of white chocolate, and a layer of milk chocolate.
Do you still use a hand-crank telephone? No? Rotary dial?

Now for the facts about what you said:
- Microsoft has NEVER said everything is going to be HTML5 and javascript. In fact, the XAML runtime is being added as a native part of Windows 8.
- Lightswitch and Access are from different teams (see the point above about different companies) But, really, what's wrong with the two approaches? I've seen lots of companies toss out two seemingly compettive products. (Ford vs. Mercury, Chevrolet vs. Pontiac vs. Buick vs. GMC vs. Saturn, Quaker State vs. Pennzoil, Exxon vs. Mobile, Conoco vs. Texaco) Currently Lightswitch is being marketed to developers (after all, it is from DevDiv), a different market than Access.
- The Ribbon came about because 80% of enhancement requests for Office were for things already in the product. The goal was discoverability. Ever since the ribbon was released, people have been complaining, "What the hell? The rest of Microsoft doesn't have it?" Now that it's in Windows, people are saying, "What the hell?"
- SOAP, while a standard, just didn't take off for most scenarios. Why? It's too complicated and has too much baggage. Remember, Microsoft wasn't the only one pushing SOAP. Ultimately, the marketplace is winning on this one.
- OLEDB, is a Microsoft format, based on COM. Microsoft is definately on the path to supporting and embracing open standards, which means ODBC. Again, this is really a win for the marketplace.

>Agreed. MS has absolutely no long term cohesive plan. They continue to thrash about.
>
>Buy VFP. Kill it. Still can't touch productivity in .NET that was had in VFP for small desktop data apps.
>
>Use WinForms. No! use WPF. No! Use SilverLight for everything. Nevermind, Silverlight is only for phone dev.... or maybe it isn't, don't ask us.
>
>Want some XAML for vectory goodness? Nevermind, everything is going to be HTML5 and javascript.
>
>Hell you don't even need to be a programmer to program. Have some Access. Better yet, have some LightSwitch. It's like Access only MVVM'ier. Mmmmmmmm, tasty!
>
>Use drop down menus. Hey, these drop down menus seem to be working pretty well. 20 years later: Fire Zee Missiles! Drop down menus killed for Ribbons UI. Guess what MS? Ribbons suck and now they're creeping into Windows 8 File Explorer! http://www.digitaltrends.com/mobile/cut-the-ribbon-why-microsoft-needs-a-fresh-start-with-windows-8/
>
>Use SOAP/ADO/ODBC/OLEDB/XML, shit we don't know! Hey, hope you didn't embrace OLEDB even though we told you to because now we're killing OLEDB.
>
>Does anybody at Microsoft know how to effing lead and present a cohesive long term strategy?!?!?!?!?!?
>
>MS isn't embracing emerging technology... it has no idea what the hell it's doing.
>
>Using MS technology is like swimming with a school of piranhas. MS business units will just as soon eat each other as they will you (the developers).