So, I've read some things about Word and Master Documents in the past, and the consensus seemed to be that they were not necessarily worth the trouble and corrupted easily. I guess, anyway.
So now my boss wants me to make a Master Document type thing for our policies and procedures manual. What I've been tasked with doing is creating a single file that collects the content of multiple individual Word files. The Main file should update whenever the individual files are updated, but someone should be able to just print off the Main file and it would have all the individual files with it. It's kind of a big project, I guess.
I have started looking into using the Master Document abilities of Word 2007, but I'm just fumbling around and haven't enjoyed the results I've received so far.
My other thought was to actually treat the whole project like a little website, with the Main page inserting the content of the subpages (like with I've done with some basic CSS in the past). The only problem with that would be that my boss wants to be able to easily edit the content of the subpages like she can in Word, so a WYSIWYG editor would seem necessary. Which editors appear/operate as closely to Word does? I remember FrontPage basically looking and acting like Word, but we don't have that (does it exist anymore?). We've got Office 2007 Enterprise, to give you an idea of some software we have available.
So, what would you recommend for this project?
Posts
I never could figure out exactly how Master Documents were supposed to work; I got terrible performance, and never could get things looking or behaving right.
What I ended up doing was creating a macro in our book template called MakeABook. It looks like this:
The way it would work is that we could each edit our individual chapters (which we kept in a SVN repository). Then, if someone wanted to stitch together a book, you would double-click the template (to create a blank document with this template) and run the macro. It throws up a dialog box asking you to locate a file in the directory with the chapter files in it, and then iterates through them basically doing a Ctrl+End (to get to the end of the document), Insert->File on the next chapter, then adds a section break. The remainder cleans up styles and figure caption styles throughout the document and inserts a table of contents at the right place.
This worked more or less fine. I had trouble because at some point one of our documents had an issue with a table style somehow bleeding out of the table and getting applied to stuff it shouldn't have, which screwed up the whole result. Some sort of weird Word bug. I eventually nuked all the table styles and that fixed the problem. The total manuscript was something like 1000 pages in our Word template, and performance was acceptable this way. Ultimately, we didn't have to worry about master document corruption and stuff because the chapters remained separate until you bound them into a full book .doc, which you could then print or email or PDF or whatever.
The problems I encountered with my brief test was that when I inserted subdocuments, I couldn't specify a continuous section break instead of a new page section break, and when I saved and re-opened the Master, it had a link to the subdocuments with some of the content loaded as it should have been... it was very strange. It also, in one case, saved content from the master into the subdocument, altering that document. So weird... but I'll admit I didn't dedicate much more than fifteen minutes to the project today.
Thanks for your help and I'll revisit this on Monday. Anymore advice/help is appreciated.
I've always avoided master documents myself. I wrote a 250 page thesis in word, and although version 2007 is much better than the previous versions, it still does bizarre and annoying things at times.
This site: http://www.techwr-l.com/articles/general/masterdocs has some good information on using master docs, if you really must.
I'd come across a few difference sources that say the same thing as Word MVP. I had actually even come across the link you provided there, back when I originally took a look at this project. I was unable to re-find that link, though, so I definitely appreciate you bringing it up.