Follow up on Handling Large Books in FrameMaker

[Joseph]

Hi Fred,

I wanted to clarify one aspect of this discussion. Is the Open All Files in
Book command causing FrameMaker to freeze and crash an unrelated issue with
the LAN and indicative of some other problem (e.g. file corruption), or are
you saying that because the LAN is causing Frame to crash when I use the
Open All Files command, I should open each file manually?

Sincerely,
Joe


On Wed, Feb 4, 2009 at 6:02 PM, Fred Ridder <docudoc at hotmail.com> wrote:

>  Joe wrote:
>
> > 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.
>
> -Fred Ridder
>
>
>



-- 
Sincerely,

Joseph Lorenzini
Naperville, IL
309-319-4487