Okay, so by moving the fields to the master page, it does indeed retain the ability to update the document from the database. The problem is that removes the multiple records per page option. So I get a 600 page document instead of 150. I can't see a run-around to this; it seems structural: put multiple record templates on the master page and you just create multiple identical records per page. I'm going to ask out loud why Adobe would introduce this function, obviously embrace it over a long period of time and leave it short of the ability to function at a pretty rudimentary level. These are major issues: you can't preview fields without destroying your document, a problem inherited from at least CS4. That's what, a decade to fix it? At least have a pop-up warning: 'Beware! Using this function will ruin your document!' Then you can't update your fields from the database, which is pretty much the point of a database... Unless you jerry-rig the document and it still doesn't function as it should. As a side note, when I went to move a record from a 600 page document to a new home, the program crashed. I just moved us to CC from CS4, and it seems more twitchy and glitch-prone. How is that possible? Just asking out loud after yet another day of dealing with Adobe errors in inDesign and Illustrator.
↧