I don't have a real clue, but I'm wondering if perhaps the status of the
inset source file could cause this to happen. This is just a wild guess:
For example, if the source file is set to read-only, or the author
doesn't have sufficient permission to access the file, or perhaps the
file is in a checked-out state from a content-management system, do
these cause the problem? We have seen that there's a problem with insets
sometimes affecting adjacent paragraphs in the container file. Perhaps a
combination of these and/or similar factors is involved.
Another thought: is it possible that the inset source files and/or the
container files belong to more than one book, or more than one author,
and there are multiple simultaneous accesses involved?
And one more: are these files on a network file server, or on a local
drive? Does the problem occur only on server-based files, or only on
local files, or no significant relation to either?
HTH
________________
Regards,
Peter Gold
KnowHow ProServices
Torralba, Jing wrote:
Hi Fred,
I'm so glad you brought this subject up.
I found the same problem in some of the files I inherited from the
previous staff. It's awful because the generated paragraph is sometimes
an AppendixNum. I tried your solution but perhaps I'm missing something
because it did not work for me. All my paratags have PgfLocked set to
No. Can you share more details? Incidentally, this is my first time to
work with MIFs.
Does anyone know if the auto-generated paratag after an inset still
shows up in Frame 7?
_______________________________________________
You are currently subscribed to Framers as [EMAIL PROTECTED]
Send list messages to [EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
or visit
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com
Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.
