Doing The “Right Thing”
Sometimes, doing the right thing is, well, the right thing to do. Other times when the Wrong Thing is done when trying to do the Right Thing, then the Right Thing is clearly and deeply Wrong.
Confused? I thought so. I will now use a clever real life example to show how Microsoft yet again does the Wrong Thing.
This time I’m not even going to bitch about the interoperability, as I’m using all MS products.
You see, it seems that MS wants everything to be passed around in HTML, or at least their version of it, to everything else. So when you copied and paste from one application, it internally formats what you’ve copied as HTML and when you paste it into another application, it pastes it in and does the Right Thing, because that application understands HTML and does what is expected, wanted and needed.
Oh if only it were true. I’m developing a web application with MS-Access (to talk to an MS-SQL Server), MS-Frontpage, testing it with MS-Internet Explorer, and communicating with the rest of the team via MS-Outlook Express (sometimes passing documents in MS-Word format), all done on an MS-Windows XP based computer. Everything should be ok right? Ha!
See, when I copy an SQL query in MS-Access and paste it into MS-Frontpage (HTML source code view) and what do I get? Not the plain, simple text that is visible in the text box in MS-Access (not formatted at all), but ugly, MS-Formatted HTML. I wouldn’t be as pissed off if it happened from MS-Word, or another app that had formatted text, but the text I copied was just in a box, no formatting, no nothing.
The only way I have found to get around this is to copy, paste into notepad, copy in notepad, and paste into your app. For some reason that removes all the “extra” formatting (or “shit” as I like to call it).