Readers of this thread may also be interested in my thread here on an expanding table crowding the elements below it:http://forums.adobe.com/message/5388909

I compared the xdp's markup files for the form that worked and the one that didn't.  I found that there was a line named templateDesigner expand {b.t.w. paste doesn't seem to work in this window right here, which is irritating}.  Anyway, in the form that did not work, this was 0 and in the one that ...

Does anyone know a good way to compare two xdp files for differences?  WinMerge seems to not be able to handle it...

Hi Bruce:I don't think I can post my form but I do have a form with a working table where everyting saves correctly.I pasted that table into my other form, and it too didn't work.Therefore, I am guessing that my problem is a *form* property and not a table property.I checked all the usages of detail...

The link to the question on its own is here, if anyone ever needs it, assuming nothing gets moved in the future:http://forums.adobe.com/message/5385949

Does anyone else have this problem?

On my particular instance of Adobe LiveCycle Designer, this is under Form Properties -> Run-time -> Scripting Box:  "Preserve Scripting changes to form when saved".  For me, I already had this option ("Automatically) selected, I tried also checking a check box at top saying "Allow Automatic Saving o...

Please help me with this.  I have a dynamic table in an xdp that can grow by adding rows (called details).  This appears to work in the browser, when I edit.  However, when I save to pdf, only the top row saves.  Any idea why the entire table is not saving to the PDF?  Thanks in advance.

Now when I save, only the top row saves (this is probably a completely different problem).  Any idea why the entire dynamic table doesn't save?I'm going to re-ask this as its own question.

Really helpful -- it did the trick.  One word of warning to other readers, while this didn't hurt the layout of my form, certain elements (such as within my own table) are absolutely ruined by setting content to "Flowed" instead of "Positioned" so this should not be used as a cure-all.  None-the-les...