Microsoft Office Q&A: Ask anything (Word, Excel, PowerPoint, etc.)

Gary Fox4 said:Is there any way to make the cursor jump to the end of the doc when I open it in Word? I just want to keep typing. Right now it always starts at the top so I have to hit > every single time.

If you're using Word, honestly, I don't see why hitting > is such a big deal—takes like a second.

But if you’re dead set on automating it, just Google "auto-position cursor at end of Word document."
Or, you could set it up using a bookmark (if it's just for one specific file). If you want it for every single doc you open, you'll need to change the default in Normal.dotm.

Alternatively, you can use some VBA code.

Kyle Johnson2 said:If we are talking about Microsoft Office—specifically Word—then I really don't see why hitting the Ctrl + end shortcut (which takes about a second) should be an issue.

Now, if you are truly hell-bent on automation, you could try searching Google for "how to automatically position cursor at the end of document when opening Word."
Alternatively, you can define it using a Bookmark (assuming this is just for one specific file). Of course, if you want this behavior applied to every single document you ever open, you would need to set it as the default within your Normal.dotm template.

And, of course, you could always handle it via VBA.

Well, thanks, man, but as a total newbie, I’m completely lost. If you could walk me through it step-by-step, I would really appreciate it.

Gary Fox4 said:Thanks, man, but I’m a total newbie here—I have no clue what you're talking about. If you could just break it down step-by-step, I'd really appreciate it.

Everything you need is right there in the tutorial, plus the link for what comes next.

- Want the cursor to jump straight to the end of a Word document the second you open it? You can automate that with some quick VBA. Here’s how you do it: 1. Hit Alt + F11 to open the editor. 2. Find "ThisDocument" in the project explorer. 3. Paste this in: ```vba Sub AutoOpen() Selection.End Key:=wdStory End Sub ``` That's it. Simple. Every time you fire up the file, you're already at the bottom. No more scrolling like a maniac.
- How do you set up a VBA macro in Word?

Look, it just comes down to what you want. You gotta decide if you actually want this action—you know, that whole thing where you jump the cursor straight to the end of your Word document—to happen or not.
Every single time I open an existing Word doc (no point doing this for a brand-new one, obviously).
Just for one specific document.

Look, I'm tapped out. Can't help you much more—unless you want me to just fix it for you, but even then, I'm stuck since I can't get into your Normal.dot file if you want this applied to all your documents.

You say you're a newbie? Stick to the shortcuts. Ctrl + end Look, you gotta get better at using Word first. If you actually want to learn, just go hit up this tutorial and follow the instructions.

- Word for beginners in 63 steps—visual guides for getting around Word 2003.
- Word 2007 tutorials.

Benjamin Wilson7 said:Finally dug some stuff up. If anyone else is stuck on this, give it a look:

Man, your code is totally freezing my entire Excel😕
Did a little digging online about this specific task and managed to round up some useful basic VBA snippets in one spot.

- Tracking changes in Excel

I'm trying to download the 2013 trial version—but when I get to the payment info stage, it won't let me select PayPal as an option. Does this mean PayPal isn't supported in the US... or what?

I'm running into a bit of a snag with Access—if anyone could lend a hand, I’d really appreciate it... I'm trying to implement an IIf function within my calculated fields : Queries by entering it into the "Field" box, but I keep getting hit with an error message. It keeps flagging the word "Big" in black. Here is the syntax I'm using; does anyone know why I keep seeing that "you may have entered an operand without an operator" error?

Size: IIf([total Amount]>50,"Big","Small")

Kyle Johnson2 said:Everything you need—honestly, everything—is laid out right there in the tutorial, along with the link for the next steps.

- Setting the cursor at the very end of a Word document immediately upon opening—yes, I’m talking about that specific little automation trick—can be handled quite elegantly through VBA. It sounds like a minor thing, perhaps even trivial to some, but when you are dealing with massive documents where you spend half your life scrolling just to reach the bottom, it becomes a matter of efficiency. Or sanity. Let's go with sanity. If you want this to happen automatically every single time you launch the file, you need to place your code within the "AutoOpen" macro. This is the specific trigger that tells the application, "Hey, now that you've finished loading this file, perform this specific action." Here is how you would structure it: ```vba Sub AutoOpen() Selection.End Unit:=wdStory End Sub ``` It is remarkably straightforward—almost suspiciously so. You are essentially telling the selection tool to jump straight to the end of the entire story of the document. Now, a quick word of caution—and I do say this with all the sincerity of a seasoned developer—make sure your security settings allow macros to run. If you have your macro security set to the highest level, nothing will happen, and you'll be left staring at the top of page one wondering why your code isn't behaving. It isn't magic; it's just permissions. Once you've pasted this into your VBA module and saved the document as a Macro-Enabled Document (.docm), you should find that the cursor leaps to the final line the moment the file opens. No more endless scrolling. Just pure, unadulterated productivity.
- So, you want to know how to actually get a VBA macro up and running within Microsoft Office—specifically Word? It’s one of those things that sounds incredibly daunting to the uninitiated, but once you pull back the curtain, it’s quite straightforward—if you have the patience for it. First off, you can't just wander into the program and expect the tools to be sitting there waiting for you like a welcoming committee. You have to enable the Developer tab first. It’s tucked away in the Ribbon settings—you’ll need to go into your Options, hit Customize Ribbon, and make sure that "Developer" box is checked. Without that, you’re essentially flying blind. Once you've got that tab visible, click it. You'll see the VBA button right there. Clicking that opens up the Visual Basic Editor—this is where the actual magic (or madness, depending on how many bugs you encounter) happens. From here, you'll want to insert a new Module. That's your canvas. This is where you’ll paste your code or start typing away at your subroutines. Now, a word of caution: if you aren't careful with your syntax, the whole thing will simply refuse to cooperate—which is frustrating, to say the least. But if you follow the logic, it works beautifully. Just remember to save your document as a Macro-Enabled Document (.docm), otherwise, all that hard work you put into your automation will vanish into thin air the moment you close the file. Simple enough, really—provided you don't trip over the technicalities along the way.

It really all boils down to one single, definitive decision—you simply have to decide how you want this specific action, namely jumping the cursor straight to the end of your Word document, to behave.
Every single time I go to open up an existing Word document—now, there’s absolutely no point in doing this for a brand-new file, obviously—but whenever I'm opening up one that already exists...
This applies strictly to one specific document—and nothing else.

I’m afraid I’ve hit a wall here—there isn't much more I can do for you—unless, of course, I were to step in and fix it personally; however, even that is out of the question because I simply cannot access your Normal.dot template if you're looking for a fix that applies to every single document you open.

Since you claim to be a novice—and let’s be honest, we all started somewhere—I would strongly advise you to stick to the beaten path. Taking shortcuts might seem tempting, but trust me, there's no substitute for the tried-and-true methods. Ctrl + end Until you get a bit more proficient with Microsoft Office—specifically Word—you’re going to find yourself hitting quite a few walls. If you actually want to master the software, I'd suggest you sit down and really dig into these tutorial instructions. It's all about the fundamentals, really.

- A Comprehensive Guide to Word for Beginners—63 Steps of Visual Instruction for Mastering Word 2003.
- Comprehensive tutorials for navigating Microsoft Office—specifically regarding Word 2007.

Much appreciated, colleague. After a bit of tinkering around, I’ll have it all figured out.

Ronald Castillo8 said:I'm running into a bit of trouble with Microsoft Access, and I was wondering if anyone could lend a hand... I'm trying to use an IIf function within Calculated Fields : Queries. I'm plugging it right into the "Field" box, but I keep getting an error message. It keeps highlighting the word "Big" in black. Here is my syntax—does anyone know why I'm getting this "you may have entered an operand without an operator" error?

Size: IIf([Total Amount]>50,"Big","Small")

Try swapping out that comma (,) for a semicolon (;) instead.

Benjamin Wilson7 said:Try swapping out those commas for semicolons instead.

I actually tried using semicolons—scattered them all over the place—but honestly, nothing worked...

Is it just me, or does it look like you wrote IIf instead of If?
Did you try typing out (.......>50;"Big";"Small")? I don't see where you swapped those commas for semicolons in both spots here.

Hey everyone.
Can anyone walk me through how to set up AutoText in Office 2003?

Benjamin Wilson7 said:Is it just me, or did you write IIf instead of If?
Did you try writing (.......>50;"Big";"Small")? It looks like you didn't swap out those commas for semicolons in both spots here.

Thanks... I added the semicolon after the 50 and after "Big"—now it’s working perfectly! (The book was actually wrong!!) It only showed a comma, though the Microsoft Access help files also suggest using a comma rather than a semicolon...
The correct function is actually IIf—with two capital "I"s and an "f"—though if you type a capital "F," the system just converts it back to lowercase for you.

Just had a quick question for you all
I'm currently using Microsoft Office 2007 in English, but I've run into a bit of a snag. When I try to switch the spelling and grammar settings over to German, it just won't work—it keeps giving me an error saying that the German language pack isn't installed on my system
Does anyone know what the best way to fix this is, or if there's a way I can get everything up and running smoothly?

Grab the German language proofing tools here

Does that come with an extra charge?

No, just head over to the Microsoft website and install it from there. You can just search Google for "download proofing tools" along with whatever language you're looking for

Ronald Castillo8 said:thanks... I tried adding it after the 50 and after the "Big" colon and now it finally works...(the book actually has it wrong)!! It said to just use a comma, but if you look at the Microsoft Access help files, it says you need a semicolon, not a comma...
The correct function is IIf (that's two capital "I"s and a lowercase "f"); you can type a capital F, but it'll just auto-correct to a lowercase f...

Glad you finally cracked the code.
Just a quick clarification here.
In all the American books—like stuff by Bill Gates, for example—Excel formulas use commas. But over here, in those exact same formulas, you have to swap that comma out for a semicolon.
- Why is it like that? Honestly, I haven't looked into it and I don't really care, so why bother? 🙂 I just learned it pretty fast (mostly by hitting my desk in frustration).
- I don't use Access all that much, but those commas in the formulas jump out at me immediately. I think I was a bit vague the first time I mentioned it because I said "replace the comma" when I really meant both types of separators.
- It’s the same deal with some of the help files and instructions I have in Excel (they use commas instead of semicolons), so they aren't really helpful to use.
hello

driftingeagle16 said:Hey everyone.
Can anyone walk me through how to set up AutoText in Microsoft Office 2003?

Using the keyboard is probably your best bet, though you could always use a virtual one.
By the way, with those recent updates to federal tech regulations, using the Microsoft Office 2003 suite is actually becoming a big no-no.
I just couldn't help myself—go ahead and roast me, just please don't hit me in the head!

driftingeagle16 said:Can anyone help me figure out how to use AutoText in Office 2003?

Check out AutoCorrect - AutoText in Word 2007. You should be able to find your way around Word 2003 since the commands are basically the same, just in different spots.

Quote : fooreest said:By the way, under the latest updates to federal IT regulations, using the Office 2003 suite
is actually banned.

??? That's an argument you might want to use.

Can someone refresh my memory on how to block or mark a specific sender as spam in Outlook 2013? It’s been a while since I actually had to deal with this kind of nonsense, and I could really use a quick reminder right about now.