Passing Parameters to Functions

I understand the principle.
But about this specific instance it does not work
How can you really change the text in the status bar in Word 2013?
Thanks
Mandy

Thanks to both Allen and Bryan. Bryan, I get why you've added your tips; you want us to do it right. And you have really good advice there. But Allen's initial tip was really helpful to me as a beginner. My issue is not about doing it right, it's about doing it at all. And the tip was simple enough that I can see a concept that I haven't really understood from other articles, see how I might actually get started. Between the two of you, well done!

Bah, sorry about the Wall O' Text. I wrote it in Word in case my browser crashed, and forgot to add back in the extra line breaks.

Couple of things here:

1) You can, and really, really should, dimension all of your variables. Instead of just "A = 12.3456", you should first have a line "Dim A as Double". (Option Explicit will avoid this error). You should also dimension variables within the function call: "Round(X As Double)". If you don’t, then you will be able to pass non-numbers into your Round function, thus causing an error. If X is dimensioned it’s a lot more likely that you will catch the error upon compiling instead of somewhere down the line. While you’re at it, you can also dimension the output: "Round(X As Double) As Double".
2) You can name the parameter when calling the function if you choose: "Status.Bar = A & " " & Round(X:=A)". Note the semicolon before the equals sign. If you use this technique, you no longer have to call the variables in the exact order. For instance, if you had a function defined as "Round(X as Double, Y as Double, Z as Double)" [terrible variable names, btw], you could call the function as "Round(Z:=1, Y:=2, X:=3)" and it would work exactly like you expect it to.
3) You also aren’t limited to only required variables. The Optional keyword allows you to make a parameter or parameters optional. These have to be last in the order of variables (in other words, you can’t have an optional parameter followed by a required parameter). Simply put, a function won’t throw up an error if you don’t put in the optional parameter. You can even give the parameter a default value. For instance, "Round(X as Double, Optional Y as Double, Optional Z as Double = -1)". If you called "Round(12.3456)", the function would still work. Y would default to 0 (the default for uninitialized Doubles), and Z would default to -1. You can also skip variables by leaving a comma, or by calling them out directly: "Round(12, , 34)", "Round(12, Z:=34)".
4) Lastly, you are not required to have a set number of inputs. If you don’t have any optional parameters, you can use the ParamArray keyword to make the last parameter a variant array that accepts any number of arguments. So You could declare a function "AddEmUp(ParamArray Nums())". Then you can call the function in the following ways: "AddEmUp()", "AddEmUp(1)", or "AddEmEup(1, 2, 3, 4, 5, 6, 7, 8, 9, 10)".
5) The fifth thing (I guess I lied about the last one being the last one) is that if your function isn’t being used to return a value, you don’t need to use an equals sign, and you don’t need to use parenthesis. Reasons for having a function like this are nuanced; however, subroutines also accept parameters, and they never return a value, so you can choose to call your subroutines in this manner. Say you had a subroutine declared as "DeleteTheCells(RangeOfCells as Range)". You could call it as such: "DeleteTheCells Range("A1:A10")".