Word and Spell Checking Redux

In the last installment, I shared an uncommon issue with spell checking in Word documents. I also shared a solution, however unsavory and tedious it may be. To recap, from time to time one may run across documents in which proofing (spell and grammar checking) is disabled in certain pages, sections and/or paragraphs.

This may be overcome by marking the problem area and selecting "Clear All Formatting" under Styles and then reformatting. While I admit that this solution is not ideal, it is certainly better than reformatting the entire document.

My approach with to the problem was the same as my approach to any other. Once the problem is identified, find a solution quickly. This solution is not usually going to be easy to implement. However, it is always workable. Once that workable solution is discovered, pass it on to the users that need to use it. This is usually met with groans, but again, it is a solution.

Then, the real fun begins. Since the users have a workable solution, I can work on a solution that is more elegant, easier to perform and implement. In this case, a macro! That's right, a macro. It turns out that the macro solution for this particular problem is, well, really short. One line of code, in fact. Create a new macro called Enable_Proofing and add the code:

Sub Enable_Proofing()
'
' Enable_Proofing Macro
'

ActiveDocument.Content.NoProofing = False

End Sub

Simply add this macro to your Normal.dot template so that it will always be available. No style clearing or reformatting required. The macro simply removes all NoProofing flags from the active document.

I love it when a plan comes together!

Word and Spell Checking

I am currently working in an office environment that has ALOT of legacy documents. What do I mean by legacy? Well, I mean we have alot of documents that were created in older versions of Word and are still used and updated with new information. All of the legacy documents were created with Word for MAC OS 9. Yeah, you read it correctly... OS 9!

So, we have all these documents and they have been modified, folded, spindled and mutilated with various versions of Word on both OS 9 and Windows. This has led to some very interesting issues. (By interesting, I mean very annoying.)

The biggest problem we have is some parts of some documents are excluded from spell and grammar check. Now, I can do without the grammer check. But, I NEED the spell check! This is a major problem, because it is not the document as a whole that is excluded. Only certain portions of some of the documents. It could be a paragraph, a table, a section or even a page. But never the whole document. This makes things very difficult.

However dim it may be, there is a light at the end of this particular tunnel and you don't have to recreate the entire document. If you are having a similar problem there is a way to get rid of these codes that are in the document, but you do not have direct access to. Believe it or not, you can mark the text in question and choose "Clear Formatting" from the Styles drop-down and this will get rid of those nasty little invisible buggers!

Why not just change it to another Style directly? Well, you can. But, if you don't clear all formatting first, the coding for ignoring the spell and grammer checking will remain! So, clear the formatting and then reformat the text to the needs of the document.

So, armed with this new found knowledge, go forth and fix those legacy documents! Show them that you're the boss!

Of Hard Drives and RAID...

Some months ago, one of the two hard drives in the server at the office decided to up and quit. Although this is bad, we use a RAID 1 setup to minimize data loss. What this means is there, in our case, two identical hard drives in the server that are"mirrored" at any given time they both have all the same information. So, if one dies the server continues to operate.

The server is getting up there in age, but I am not ready to go to a new Server OS and you can throw all the power you want at Windows Server 2003 32bit and not see much in the way of performance gain for network-centric operations. So, I decided to upgrade the hard drives with a pair of new server-grade Seagate 500gb 7200.11 SATA drives. Mmmmmmmm a slight performance gain, a huge storage gain and cheap. While the server was down and I was under the hood, I decided to bump the RAM from 2gb to 4gb. Yeah, I know that it can't use all 4 gigs but it can use slightly more than 3GBs and it also was pretty cheap.

The upgrade went relatively without a hitch. I booted from a BartPE CD I have with my RAID driver floppy disc (yes, a real 3.5" floppy) and made an image of the partition. Then I installed the new drives, created the new Array and restored the image. It took about an hour.

But here we are a few months later and one of those new drives has failed. No big deal right? Well, it is when the RAID controller Docs don't discuss rebuilding the array. Now, don't get me wrong, this cheap SATA RAID controller has saved me alot of greif up until this point. But, REALLY?!? No docs on rebuilding?!? REALLY?!?

If you find yourself in a position that requires you to rebuild an array then keep this in mind. An OFFLINE RAID rebuild means that you will be rebuilding the array in the BIOS without the benefit of the OS, Internet, Solitaire, etc. So, if you have to rebuild an array and want to has access to all of those wonderful things that make computers worth having make sure you choose ONLINE rebuild.

All of that said, I don't trust it. Choosing an ONLINE rebuild with a cheap controller seems a bit like rolling the dice. Its an OFFLINE rebuild for me! So, I'm sitting back and checking my webmail periodically.

Cheers!