> Based on what you and others have said, it certainly sounds like the LAN is
> the culprit, not FrameMaker.
Yes. And the workaround that several of us have suggested (opening all
the component files before doing book-level operations) is still valid,
That approach will eliminate the multiple, very slow open-update-save-close
cycles that have to occur in the background if the files are not open
during the updae book operation. I know you've said that the Open All
Files In Book command chokes, but you will still save a lot of time in the
long run if you take a fee minutes to manually open each file. And there
are several approaches you could take to scripting this if manual opening
is too tedious for you.