I'm not sure, but I think the field doesn't update when you open it..displays what it last showed when you closed it. The Update Fields macro in Relative path works only: 1. This may be by design, but I don't know why it's a good design.
If I'm the one responsible for putting out the Newsletter, I like to Be In Control, so my Host document sets the rules.If, however, I'm just a minion, then I like to rest responsibility on someone else's shoulders, they should govern the formatting through their Host document. You need to be pretty dexterous with (a) updating your field application by selecting the text and tapping the F9 function key and ([img]/forums/images/smilies/cool.gif[/img] (while you are experimenting in the Host document) clearing local formatting by selecting the text and using Ctrl-space. "Stencil") to a selected field re-introduces the MERGEFORMAT switch; this will cause problems to you if you had planned to use the CHARFORMAT switch. The nicest thing I can say about introducing a MERGEFORMAT switch in addition to a CHARFORMAT switch is that it is an undocumented feature, since the Help files don't say what is supposed to happen when both switches are in place. You don't want to hear what else I've said this past weekend.I have supplied an Update All macro (Red Eye button on the Host toolbar). Introducing MERGEFORMAT switch where there was none can not always be considered a bug, since MERGEFORMAT is sometimes the default switch. I suggest that you use lower-case letters for your switches, which makes it easier to spot the Merge Format cuckoo when it hatches.What's really weird is that a recording (Tools, Macro, record) of the change of font doesn't show any hint of MERGEFORMAT, and that my YELlow macro - s tripped down version of a recording - doesn't introduce the MERGEFORMAT switch. The Bottom Line, the proof of the pudding, is your observation of what happens in your Host document when you tap the F9 function key to update fields; after all, this is what happens when you transmit the document to another medium, whether you are Updating Fields When Printing (Tools, Options, Print, Update fields), or handing the document to another user.I also mentioned that if the source & target document were in the same folder, that you could use: Several people have said that using a relative path like that would give an error message. I wonder if someone who has access to other versions of Word could verify my observations.
Open not pointing to Stuart Temp Right click the included text and update works fine Open another file in another folder from the File Open menu Right click the included text in and update now gives "Error not a valid filename" Stuart R Thanks, Stuart.
The associated document (C: Temp Source.doc) contains formatted text for inclusion. There's only MERGEFORMAT and CHARFORMAT; if you don't specify a format, MERGEFORMAT is the default if you travel the "Insert Field, Links and references, Include Text" route, but is omitted if you travel the "Insert File, Link" route.
For ease of installation you can place both documents in your C: Temp folder. Word97SR2 will occasionally toss in a MERGEFORMAT for free (observations 9 and 11 below), just to keep the CHARFORMAT company. You'd think that means only two options, but see Observations 11 and 12 below. Use one of MERGEFORMAT and CHARFORMAT; if one doesn't work, use the other one.
If I use relative paths & you place them all in the same folder, they still won't work..so it seems, unless you switch to that folder under File/Open. Or maybe there's a better way - I'm not sure anything's gained by using in the macro.
Cheers Hi Phil, I tried bookmarking just the path part of the string returned via , but it get's clobbered as soon as is updated, and I couldn't include the drive letter without selecting the whole field.
If I then choose File Cancel and try to update fields again I get the error. Then you'd need to convert the path backslashes to double backslashes - because that's how they have to be input in the field.