Seems that I have found an answer. I thought that I tried this, but I forgot that I had a DIFFERENT routine putting a graphic inbetween two of the tables and the graphic should have been the last table -- and, so, everytime that I saw the graphic in between the two tables, I thought that I had the same problem since the table content all looks pretty much the same. So I may have fixed the problem hours ago and just kept on trying to solve it again... Aarrgg...
So while I still really don't understand WHY any tables go whacko after the overset, here's what fixed it for me when adding another table:
(where tf = a TextFrame)
Hope this helps someone.
1 person found this helpful
There is actually a valid reason, AND a good solution that will always work.
The tables are inserted at the "end" of the frame. If you add one below the last visible table, then (logically) it will appear *before* all overset items.
The trick is not to rely on your textframe size. Add your items at the end of textframe.parentStory, and it will no longer matter how much you have in a single text frame.
Thanks for your reply. I'm honored! :-) Sorry for the delay in getting back to you (posting on other forums as you know! ;-))
So I had an "AHA!" moment upon reading your reply..
EXCELLENT point making perfect sense -- so I tried it -- but I think that I must be doing something whacky as I am referencing the ParentStory but getting an error message -- something like "expecting ..(misc objects)...'Story'.... but received 'Story'. I was getting this last night too before I gave up and went to sleep. :-)
I will try to get back to you with some MUCH clearer info shortly. Just didn't want you to think of me as inappreciative.