🚀 go-pugleaf

Can you check it in?

If not, I'd copy all the content into a new file and save that. You may want to use a slightly different file name, maybe incrementing the problem file with a number or something so you can tell them apart.

Art

I checked it into Perforce and checked it out again - made no difference to the file behavior in FrameMaker. I also closed Frame and rebooted hoping it would go away.

Because the file is under source control I'd rather not write to another file. The workgroups interface doesn't show Select all in flow or Save As - so doing it will be pretty hard.

Tom

Tom, do you have a stray *.lck file matching the problem chapters? Those are the network file lock files that FM creates when you hae networking turned on.

If so, try renaming it (rather than delete) to see if the lock goes away; if things work properly then delete them.

Thanks for writing, Sheila. I deleted lock files, but there aren't any stray lock files now for the affected files.

If you look at the .fm file in File Explorer, and right click-on Properties, what does the Attributes > Read Only box have marked (is it black check, gray check, or no check at all)?

Read only is NOT checked in Windows file properties.

When you update the book, FrameMaker reports that an affected file is View only. Evidently, there is a value Frame can write in the file that marks it as view only (found a knowledge base article about this). You can set it manually in a MIF file.

I can't Save As an affected file, so that's no help, unfortunately. I'm guessing that the workgroups functionality sets that value.

Thanks again, Sheila - maybe we'll figure it out yet. If nothing else, I can revert the files, but that will cause other problems.

There's a thing called "heroic open" that you might try with the individual files -- unfortunately I've forgotten the keystrokes for it, but if you search this forum for that term you'll find it. It's a bit of a long shot, but it can't do any harm.

Long shot #3, try making a brand new, temporary, book and adding one of the problem chapters, to see if it behaves any differently in another book.

Thomas,

Try <esc> F l (lowercase L) k to unlock the document in FM.

Thanks, Arnis: <esc> F l (lowercase L) k did the trick.

I was doubtful, I found and tried the tech note on this method earlier today, but it didn't work. Must have been a slip of the finger. So glad I read your note and tried it again.

Thanks again for the suggestions Sheila - I'll have to look up heroic open.