AnsweredAssumed Answered

Go Text Field Spanning More Than One Page Misses Some Content When Printing

Question asked by disabled_jmkimmel on Jun 7, 2013
Latest reply on Jun 7, 2013 by Mike_Mitchell

I have a large comment field that is formatted to stretch over multiple pages if necessary when printing.


FileMaker Pro renders correctly due to a fix for this problem in 11v3 but the Go client will trail this field into the page footer, then cut off the first line of the next page. Does anyone have an elegant (or brute force) method for handling this situation?


I have sliding turned on so it won't take up a lot of pages when the field doesn't have a lot of data in it. Since this is the case, using calc fields to chop the field into parts won't work.


The only thing I can think of is to accumulate the data from the text fields in the different records in the found set into a global variable or field and then come up with some kind of calc that would chop that into parts.


Has anyone already tilted at this windmill?


Thanks in advance,


John Kimmel