Turning off Date AutoComplete in Word 2007
In microsoft.public.word.docmanagement, someone complained that Word 2007 offers to autocomplete days, months, and dates. Someone responded by posting the following URL, http://office.microsoft.com/en-us/word/HA100997751033.aspx, which explains that it’s Word’s AutoComplete feature, and cannot be turned off. That would be fine–if it were actually true.
As it turns out, there actually is a way to turn this off in Word 2007, the statement to the contrary in that article notwithstanding. If you run the following macro, date AutoComplete should no longer occur:
Sub TurnOffAutoComplete()
Application.DisplayAutoCompleteTips = False
End Sub
Or, if you prefer a toggle, replace False with Not(Application.DisplayAutoCompleteTips).
The problem was that AutoText autocomplete was causing problems in the Office 2007 beta because of the way Building Blocks were implemented. So, autocomplete for AutoText was removed. In Word 2003 and earlier, the autocomplete checkbox control both dates AND AutoText. In Word 2007, they disabled autocomplete for AutoText, but left it enabled for Dates.
At the same time they removed the checkbox from the interface, they nonetheless left the command in the object model. Hence, you can use this command to turn off the parts of autocomplete that were NOT removed.
Turning off the Mini Toolbar
In Word 2007, when you make a selection, the Mini Toolbar, shown below, appears. When you right-click in a document, it also appears.
Word’s interface provides a way to prevent the Mini Toolbar from appearing when you first make a selection. However, the interface does not provide a way to prevent it from appearing when you right-click in a document.
To turn it off when you first make a selection, choose Office->Word Options->Popular, and remove the check next to Show Mini Toolbar on selection–the very first option–shown below.
What about the rest of the time? Thanks to fellow MVP Tony Jollans, I now have the answer. Simply write a one-command macro with the following statement:
Options.ShowMenuFloaties = False
This turns “floaties”–Microsoft’s name for the Mini Toolbar–off. If you’d prefer a toggle, instead, use the following:
Options.ShowMenuFloaties = Not (Options.ShowMenuFloaties)
This one toggles the Mini Toolbar on and off. I just created that macro and assigned it to Ctrl+Alt+Shift+F. Now, anytime the Mini Toolbar gets in the way, I can toggle it off. If I decide I want to use the Mini Toolbar, a quick press of Ctrl+Alt+Shift+F turns it back on.
Errata: Full Screen not really RIP
In the microsoft.public.word.docmanagement newsgroup, Martin Gifford pointed out that I mistakenly indicated that Full Screen view (not to be confused with Full Screen Reading View) had been completely removed from Word 2007. Indeed, on page 858, in the Word 2003 > Word 2007 commands appendix, I indicated that View->Full Screen was RIP. This is not correct.
In defense, I based this on information deduced from Microsoft’s Interactive Applet that shows where Word 2003 commands are located in Word 2007. If you choose View->Full Screen in the applet, you see this:
Notice that View and Full Screen Reading are both highlighted. Since Full Screen Reading and Full Screen aren’t the same, this allowed me to incorrectly conclude that Full Screen was no more. Searches in the command list in customizing the Quick Access Toolbar had turned up empty in searching for the legacy Full Screen or View Full Screen commands.
Oops.
I should have been searching for Toggle Full Screen View, instead:
As you can see, it’s not gone. You can add it to the Quick Access Toolbar if you like. Or, you can press Alt+V, U, and voila! The legacy keystrokes work. Thanks to Martin Gifford and Tony Jollans for pointing this out.
Where is Prompt for document properties in Word 2007?
In the microsoft.public.word.docmanagement newsgroup, someone asked:
In previous versions of Word, you could turn on an option to display the properties dialog box every time a new document was saved. Pretty easy.
In Word 2003’s Tools->Options->Save tab, you could tell Word to prompt for document properties
Who can tell me how to do this in Word 2007. Can’t find the option anywhere.
In the Developer tab (if it’s not showing, turn it on in Word Options->Popular), click Document Panel. At the bottom of the Document Information Panel dialog box, tick the Always show document information panel on document open and initial save option.
Making Word 2007 a Little More Familiar
Moving from Word 2003’s toolbars and menus to Word 2007’s ribbon can be a bit of a shock to many users of earlier versions of Word. Some of this shock can be eased, however, by making your most-used tools from Word 2003 as visible as possible in Word 2007.
Contrast the interfaces for Word 2003 and Word 2007. Here, I’ve told Word 2003 to show the Standard and Formatting toolbars on two rows:
Notice that right above the ruler, you see the style name, the font name, and the point size. For the most part, no matter what you’re doing in Word, this information is always there where you can see it.
Now, take a look at the default view for Word 2007:
Here, too, you see the style, font, and point size, at least initially. However, if a style other than the ones that fit in the current style gallery window is one other than the first 4 or 5 (sometime more, sometimes fewer), then the current style name isn’t available to the user. Moreover, if you move out of the Home tab, style, font, and point size are no longer knowable at a glance.
I’m guessing that the programmers at Microsoft aren’t writers. I can tell this because no veteran Word writer would put up with not knowing at all times the current style, font, and point size. These are vital pieces of information. Well, perhaps you don’t agree. If you don’t, then this post isn’t meant for you. It’s meant instead for users who want to know at all times what’s in their document.
A solution is at hand, however, in the form of the Quick Access Toolbar, or QAT as it’s more affectionately known. First, look at where the Quick Access Toolbar is. It’s up there in the stratosphere, thousands of miles above where you’re working. This means that to see it, you’re going to have to look way above where you’re accustomed to looking. It also means that you’re going to have to move the mouse quite a bit more than you did when accessing the Formatting toolbar in Word 2003 and earlier.
So, let’s move it. Right click the QAT and choose Show Quick Access Toolbar Below the Ribbon, as shown here.
Great. Now the QAT is closer to the battlefield, even if the selection of tools is somewhat lacking. Let’s address that problem right now.
First, let’s add a style tool to the QAT so you can see what you’re wearing, so to speak. Right click the QAT and choose Customize Quick Access Toolbar. Set Choose commands from: to Commands Not in the Ribbon. Click in the list of commands and tap the T key to accelerate to just below the last command that starts with “S”. Scroll up a few commands and look for one that says Style. When you hover the mouse pointer over it, you see this:
The word Classic is the clue that you’re in the right place. With Style selected, click Add to move the command into the right-hand panel. Click the up arrow (5) to the right of the right panel until Style is at the top:
Click OK. Let’s see what it looks like now:
Great! Now we can always tell what style is applied at the insertion point. Not so great, however, is that unless the Home tab is displayed, you can’t necessarily tell what font and point size are selected. Let’s fix that.
In the Home tab, right click the font tool’s dropdown arrow, and choose Add to Quick Access Toolbar. Next, right click the point size tool’s dropdown arrow and choose Add to Quick Access Toolbar.
This done, you’re almost there:
But, there’s a visual problem. If you came here from Word 2003, you’re used to the three tools–style, font, and point size–being side by side. Click the dropdown arrow at the right end of the Quick Access Toolbar and remove the checks next to Save, Undo, and Redo. You’ll have to do this in three motions, since the dropdown list doesn’t remain displayed.
Once that’s done, the three formatting tools you added will now be side by size. Now you can click the dropdown arrow on the Quick Access Toolbar and put those tools back. They’ll be added to the right of point size, rather than where they were.
If you like, you can set up the newly positioned Quick Access Toolbar as a combination of Formatting and Standard toolbar tools so that the tools you need most often are right in front of you:
From left to right, we now have: Style, Font, Point size, New, Open, Save, Bold, Italic, and so on. But, notice which ribbon tab is selected: Review.
Now, no matter which ribbon tab is displayed, you’ll always have those tools at the ready. But, most important, if the style, font, or point size in the current document ever look a little strange to you, you’ll be able to tell at a glance what’s what.
Bigger matrices using the Linear method for inserting equations
As shown here, Word 2007’s equation interface provides a maximum matrix size of 3×3:
So, what if you need a 3×4, 4×4, 4×3, or some other size matrix? Are you out of luck? Not at all.
Begin by inserting a 3×3 matrix as shown above. What you see in your document is shown here, minus the “Click here” balloon:
Click as shown to drop down the control menu for the equation object for the choices shown at the right. Click on Linear.
This now exposes the ugly syntax for creating a matrix using the linear syntax:
So, what does this mean? Well, first of all, you’re not seeing the entire picture. What’s missing is the full syntax. If you could see the full syntax, you’d see:
\matrix(&&@&&@&&)
& corresponds to columns, and @ corresponds to rows. For x & characters, you get x+1 columns. For y @’s, you get y+1 rows.
When modifying the syntax to add additional columns, it’s easy. Just add a & as shown here:
(&&&@&&@&&)
Now, right-click the equation and choose Professional, and you’re rewarded with:
Right-click again and choose Linear, however, and you’ll see that Word automatically completed the syntax for you:
(&&&@&&&@&&&)
That’s because ragged matrices aren’t allowed. What’s a ragged matrice? Had they been permitted, the modified matrix using (&&&@&&@&&) would’ve looked something like this:
| Â | Â | Â | Â |
| Â | Â | Â | Â |
| Â | Â | Â | Â |
Â
So, if you wanted a 4×4 matrix, what would you do? Insert a 3×3 and modify like so:
(&&&@&&@&&@&&)
Notice that I’ve added another column, and I’ve said to include 4 rows in that column. But, I haven’t added additional &’s in the other parts of the syntax specification. Nonetheless, when I right-click the equation and choose Professional, I now get this:
If I now flip this back to linear, I see that Word graciously filled out the needed syntax for me:
(&&&@&&&@&&&@&&&)
When going the other way – shrinking an existing matrix – you would need to completely modify the syntax. Word isn’t smart enough to sense that you’ve removed an & and now want a bunch more removed. But, frankly, if you want a smaller matrix, just use the built-in user interface.
Creating New Word 12 Files from Windows Explorer
A few days ago, in one of the public newsgroups, someone posted about a problem when creating new Word files in Windows Explorer. First, set your default font in Word to something other than Calibri 11 point. To do this, press Ctrl+D, select a different font and/or point size, then click Default. Click Yes to changing the default. If prompted later, say Yes to saving the changes in Normal.dotm.
Next, try the following:
- In Windows Explorer, right click in the files area and choose New->Microsoft Office Word Document.
- Type a name for the file, the double-click to open it.
- Regardless of your own default font and point size, Word will have created a file that uses Calibri 11 point as the default font.
Now, try it again, only this time choose New->Microsoft Office Word 97-2003 Document. This time, Word will correctly use your defaults, rather than its own hard-coded Calibri 11.
CAUTION: Editing the registry can damage windows and prevent your computer, office, and word from starting. It can also put out an eye. Edit your registry at your own risk.
The behavior for Word 97-2003 documents is controlled by the registry’s settings for what it does when you create a new .doc file in the “shell” (Windows Explorer). This is controlled by the following registry location:
HKEY_CLASSES_ROOT\.doc\Word.Document.8\ShellNew
In particular, it’s controlled by the FileName variable, which tells the system to look for WINWORD8.DOC, contained in the \windows\ShellNew folder.
If you look down a little later, however at:
HKEY_CLASSES_ROOT\.docx\Word.Document.12\ShellNew
there is no FileName variable. So, when you create a new .docx file this way, Word sees that there is no reference template or file, and it uses its own internal default Calibri 11 rather than the user’s default font settings.
A partial fix for this behavior is to create a new FileName variable in the docx registry location, pointing to a file that contains the desired default fonts, such as a file you might name WINWORD12.DOCX (you would need to create that file, too, not just a pointer to it). Then, when you create a new file using the NewðMicrosoft Office Word Document method from Windows Explorer, it will use the defaults contained in that file (WINWORD12.DOCX, for example).
This does not solve the whole problem, however. That’s because when you change the default font in Word 12, it stores the new default in Normal.dotm and in WINWORD8.DOC. The change doesn’t get communicated to your WINWORD12.DOCX.
The obvious solution is to point the .docx\Word.Document.12\ShellNew FileName variable at WINWORD8.DOC, right? Well, that is what logic dictates. However, when you do that and create a new file, the resulting file cannot be opened by Word. So, FileName has to point to a different file.
You might be tempted to point FileName at Normal.dotm in its default location. This, too, doesn’t work. It tells you that the folder is in use, creates two new files (instead of one), and both use Calibri 11 regardless of your default settings. So, unless someone else discovers a different work-around, we’re left with half a solution.
Of course, if you create new files from within Word 12/2007 itself, then you don’t need this solution. You need this solution only if you’re addicted to the Windows Explorer method. In a later article, I’ll look at other solutions.
Repost from 3/8/2007
March 8, 2007
Dian Chapman, my technical editor for the Word 2007 Bible, tells me that her two copies of the book arrived yesterday. I still haven’t seen any yet. I emailed Jim Minatel (my AE) to find out why not, and he tells me that the first printing is already out of stock! They’ve ordered a second printing, which will be ready next week. Amazon, Barnes & Noble, Wal-Mart, and other online booksellers seem to have it in stock. So, Wiley’s warehouse loss is their gain. If you order the book now, there should be no delay in its shipping to you.
On the computer front, I ultimately determined that either the motherboard or the GeForce 7300GT was defective. I exchanged the T470 for a different one, and this one has been working like gangbusters. I sure wish I hadn’t invested five days trying to get it to work. But, at least I now have a better idea about how to recognize defective hardware… as opposed to defective Vista drivers. Even so, I’m still gun-shy about installing new versions of the driver.
My most recently solved Vista mystery—apparently—was the presence of an error in my events log:
The following boot-start or system-start driver(s) failed to load: i8042prt
I searched the internet, and didn’t find much specific having to do with Vista. However, in an old Windows 2000 discussion—in Spanish, no less—someone indicated that you see that error message when your mouse and/or keyboard are connected using USB rather than the PS/2 connectors. So, apparently, it’s nothing to worry about. I’m blogging about it here so it might be useful to someone else when they search for the error message.
Another pending mystery—and I hope it doesn’t recur—is why my computer suddenly started saying that my Documents folder was off-limits this morning. This morning while editing an Excel spreadsheet, I suddenly got an error message that the file I was editing was in use and that I couldn’t save to it.
Because I didn’t want to lose what I was doing, I decided to take a quick screen shot. When I tried to save the screen shot, I was informed that I didn’t have permission to access my Documents folder. So, I grabbed the camera, and took a picture of the data onscreen as a last resort.
During this time, the computer was responding extremely slowly, but I didn’t see anything grabbing the CPU in the Task Manager.
I closed everything and rebooted, and the problem has not [yet] recurred. I studied the event logs, but I don’t see anything that happened during that time.
I have two suspicions so far, neither of which are based on anything solid:
- My first suspicion is that it has something to do with having installed NOD32 last night — always suspect the new guy, right? — but, that’s just a desperate grasp.
- My second suspicion–this is a new computer with an Intel Core2Duo 6300–is that the CPU developed schizophrenia, and that possession of everything disk-based resided in one of the cores and was claiming ownership of my user files and folders, while the other core had suddenly assumed control of the program memory space, and wouldn’t let me access anything because the other core “owned” it.
In months and months of beta testing Vista and running RTM, I never had anything like this happen. But, all my testing/running until this past Tuesday was with a single core Pentium 4, and my A/V software was AVG, not NOD32.
Anybody seen anything similar?
My next adventure is to decide whether to replace Vista Home Premium with Vista Ultimate. Actually, I already know that I’m going to do that. But, I think I’ll install my large SATA, first, and install Vista Ultimate on it. Now, I’ll need to decide whether to install the 32 bit or 64 bit version… or both—maybe one to my X partition and other to my Z partition.
I also want to boost my RAM to 4 GB. It turns out that the 7300GT actually uses shared memory—robbing almost 500MB from main memory—in addition to its own 256MB. Greedy little sucker. I could try to turn off this sharing, but when I did that on the defective T470, my graphics index score went from 4.3 down to 1.0! So, I think I’ll try the upping-the-memory solution, instead.
Redaction in Word 2007
If you look in Word 2007’s Help under redaction, there is an entry for the Microsoft Office Word 2007 Redaction Add-in. Sounds good, right.
Well, as of March 13, 2007, it doesn’t exist.
If you click the link to download it, you’ll get:
The download you requested is unavailable. If you continue to see this message when trying to access this download, go to the “Search for a Download” area on the Download Center home page.
If you search, you’ll discover an add-in for Word 2003, but none for Word 2007. And, if you download it and try to install it in Vista, you’ll get an error saying that you need to install .NET Framework 1.something. Well, by default, Vista includes .NET Framework 3.0, and apparently, that’s not good enough for the Word 2003 redaction tool. If you thought that having version 3 would include the ability to run items requiring version 1, you’d be wrong at least in this case.
Meanwhile, over on my laptop, which is running Windows XP and does indeed have the requisite version of .NET Framework, it installs just fine. This should let me see if it works in Word 2007, since my laptop has both Word 2003 and 2007, right?
Amusingly, at the Installation Complete screen, the Redaction Add-in setup program includes the ironic notation:
This add-in is built on the Microsoft .NET Framework. Please use Windows Update to check for any critical updates to the .NET Framework.
Yeah, right. But, not .NET Framework version 3.0, I guess.
All installed… um. Well. I see it the files in an offshoot of the Program Files folder. But, not only is it not showing up in Word 2007, it’s not showing up in Word 2003, either. Not there after rebooting, either.
Well. I don’t have the patience or time to play with it now. But, it’s not looking good for redaction in Word 2007, even if you happen to have the correct version of .NET Framework installed. It looks as if Microsoft expected to have it ready in time for Office 2007 RTM, but didn’t make it.
Word 2007 and Word 2003 Coexisting
If you’ve ever used two recent versions of Word on the same computer, you know doubt have encountered that infuriating dialog that tells you to wait while Word is configured. You use Word 2003 for a little while, and then you switch back to Word 2007, and you get the “Wait, while…” yet again–multiple times in the same session.
Until now, I thought that the only way for two versions of Word to peacefully coexist was if one of them always loaded using the /a switch. Among other things, this meant that the /a version would not be able to use any of your custom settings (except for Word 2007’s Quick Access Toolbar settings, which seem robust with respect to /a).
It can now be revealed, however, that there’s an easy registry solution that allow multiple versions of Word to exist, and for you to have your various customizations remain in play as well.
Caution: Edit your registry settings at your own risk. Incorrectly editing your registry can damage Word, Office, Windows, your community, the planet, and the universe. For additional information on how to edit your registry, consult Google. I’m assuming here that you know what you’re doing, and hence will give you only the bullet. It’s up to you to buy your own gun.
Note: Do not do this if you’re running just one version of Word! Otherwise, occasional and useful self-repairs won’t happen.
Now, for the juicy bits. You’ll need to add a NoRereg DWORD (32-bit) value to the Options section for each version of Word that you want to run. In Office 12, this value goes here:
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Options
After you create the NoRereg value, set it equal to 1. And you’re done!
Repeat this for each additional version of Word you plan to run. For Word 2003, for example, the place to add the NoRereg value would be in:
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Options