file u tried to open was not found.It may be missing.-->string/ mF

[pintree3]

I read im numerous reliable web sites the following tip: to make a shortcut
so that Word automatically opens the last file used one should create a
shortcut with the following: string/ mFile1
So I created --> "C:\Program Files\Microsoft Office\OFFICE11\WINWORD.EXE"
string/ mFile1
However, when I use the shortcut for Word 2003I get an error message that
says, "The file you tried to open was not found. It may be missing....."
You click on OK and the file in question load up anyway, disregarding the
obviously false message since thew file was found and loaded. So how do I
avoid getting this nagging pop up window and have the short cut simply do
what it is supposed to do?

Thank you
Mich

 

[JohnR]

Go here:
http://support.microsoft.com/kb/q210565/#XSLTH3140121122120121120120
John

 

[Suzanne S. Barnhill]

I'm not sure where you're getting the "string" part of the syntax, as this
is not included in the instructions in "How to use startup command line
switches to start Word 2003, Word 2002, and Word 2000" at
http://support.microsoft.com/?kbid=210565

 

[pintree3]

thanks for taking the time t reply.
Ou say it doesn't state this yet it does. At the very end of the page you
suggested it says,
"The following Word startup (command-line) switch is listed in Word 2000
Help but not listed in Word 2002 or Word 2003 Help.

Type To do this /mfilen Starts Word and then opens the specified file on
the Most Recently Used (MRU) list on the File menu.

So you see it does give this exact command line string--yet it does not work
in Word 2003.

 

[pintree3]

Thanks

on the page sited it does give the command switch--> /mfilen Note however,
thta there is a small-lower case 'f' and not upper case. I tried it in lower
case and the same error message occurs BUT without the file showng up this
time. Meaning it is wrong on the microsoft website. also it does not say to
write (as I have), string/ mFile1 but only mfilen (where n I assume is a
number). I have tried it without writing 'string/' and it did not work. The
only one that does work is to write it exactly as I have written it except
for the fct that it gives me that wrong error message. BTW it worked fine in
previous versions of Word.

 

[Suzanne S. Barnhill]

In that case, I have no clue, assuming that the path you are using in the
command line is the actual path to Word on your computer and that you are
leaving a space before the forward slash and none after it.