I believe your belief is a misinterpretation of what is actually happening. If you have the network file locking feature turned on, there will be a .lck file for every file you open (not just the book file) exactly as Syed described.
But the point is that you do not need to put up with .lck files _at all_ unless your files are located on a shared network drive and unless there are other people who could potentially open some of those files at the same time that you are working on them without telling you. If the files are on your local system (i.e. are not accessible to other FM users), if they are in a content management or configuration management system, or if you are the only FrameMaker user at your company, there is no reason at all to have the network file locking feature turned on. -Fred Ridder > From: gflato at nanometrics.com > To: Syed.Hosain at aeris.net; framers at lists.frameusers.com > Date: Wed, 19 May 2010 11:24:34 -0700 > Subject: RE: Frame 8 bug > > I believe that when you update your book file, if lck files exist for chapter > files, Frame crashes. There should only be an lck file for the book file, not > the individual fm files within the book. I only have the book file open and > am trying to set the conditions for it, yet all these lck files from the > frame chapter files keep opening and then Frame gets the dreaded Internal > Error bug and crashes. _________________________________________________________________ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
