🚀 go-pugleaf

I hope nobody minds my "thinking out loud" here.

Your example, Ole, is very helpful.

The only reason I'm thinking of using a second document to make the table is because I am fearful that a document that already has 2538 stories in it might be overwhelmed if I also add a table that has 20 columns and 480 rows, with just about all cells populated.

But maybe I should throw caution to the wind and just go ahead and build the thing on a new last page. I can always insert logic to use a second document if my fears materialize into real problems. The thing is: while the data for most rows is contained on a single page, for some there are two pages involved and in another case three.

Hmm. Can you move three pages at once so that the text frames stay threaded? I'm not sure.

I guess the first thing I need to do is work out the syntax for moving some text from a paragraph to a cell in a table. OK, I'll try a test where the insertion point is in the paragraph and there's only one table.

Hmm. What's wrong with this:

myTargStory = app.documents[0].stories.item('Target');
myTargTable = myTargStory.tables[0];

I only split it into two lines because I couldn't get a single line to work.

Hmm. Even myTargStory.tables doesn't work; results in "Object is invalid".

Perhaps one of Ole's examples uses a table. Off to check.

Dave