> This only happens with a specific table.
If you can isolate the trigger factor, that would enable two things:
1. other FM users, some with Support, could confirm and re-report,
2. Adobe would be able to find the root cause quicker.
Is it a specific Table Catalog table, regardless of content, or
specific table content regardless of table format?
Possibly unrelated anecdote ... as I've mentioned, when we get Err7103
crashes, it's often well after the real damage has already happened.
We have seen cases where huge sections of a document appear to
vanish. In at least one instance, the content did not disappear.
It got moved into a table cell, and was largely invisible.
I can imagine that hidden table structures of sufficient complexity,
or sufficient degeneracy (e.g. unbalanced tags, garbage structs,
containing cross-refs to self*), could make the document unstable.
________
* When the size of the .fm file increases with every save (and no
changes), circular cross-refs are a likely cause.
