There is a "full" event you can make use of, it might help.http://help.adobe.com/en_US/livecycle/9.0/designerHelp/index.htm?content=000763.htmlhttp://blogs.adobe.com/formfeed/2009/04/field_tab_on_full.html

It sounds like one of the subforms is not set to allow page breaks. Not sure why the pagination tab would be greyed out.

Take a good look at the structure of the sample above. All of the subforms that need to move need to be in flowed subforms. You have objects outside of the subform that is flowing. You may need to wrap the entire structure in a flowed subform or move the objects that aren't flowing into the subform ...

Here's an example: http://www.assuredynamics.com/index.php/portfolio/expanding-objects-in-flowed-subforms/

I'd take a look at regular JavaScript sources, there are some examples around. The math is a bit much for me...http://stackoverflow.com/questions/5616600/time-interval-in-15-minutes-increment-formathttp://stackoverflow.com/questions/4968250/how-to-round-time-to-the-nearest-quarter-hour-in-javascript

You can mix JavaScript and FormCalc without changing the form settings. You just can't use them in the same event. You can switch the language in the Script Editor.

On the "-" button use this.parent.parent.index to get the index of the row the button is in. the "parent" reference is used to move back up the hierarchy so if you had say a subform around the button in the cell you'd have to add another parent to find Row1.So to delete the row try: _Row1.removeInst...

The (this.parent.parent) is looking for the object that is breaking across the page, in your case the table - you should also be able to put the name of the table in there too.I just copy and pasted that from a place I've used it before - in my case it was a button I was changing the caption on. So ...

I'm not sure what's happening. I've not tried doing this before so maybe someone else will have a better idea.You might be able to re-hide elements when the table breaks across a page, you can check this with pageSpan(). Try it on the layout:ready event.if (xfa.layout.pageSpan(this.parent.parent) > ...

The problem with columns is that there aren't any. Tables are just a series of repeating subforms, there's no column to operate on.I've never had to try doing it but I've seen some methods for handling it. Here's one: http://forms.stefcameron.com/2006/10/28/scripting-table-columns/