If there are no sliding fields, put three vertical line objects on your layout, one the header, one in the footer and one in the body. Align them to look like a single line. Make sure that the line in the body does not touch the boundary lines between header-body and body-footer.
Thanks for your help.
I followed your instructions, but the line still does not go all the way through the end of the body.
Please see enclosed file.
What am I doing wrong?
Is this layout in list view, with the text shown at the bottom in the footer?
Regrettably, I don't know of a way to get the "no man's land" between the last record and the footer to show that vertical line.
This might be an old post, but I just come across at the same situation as David Arias.
As a matter of fact, I've done this maneuver in fmp11 quite well, by extending the vertical line into the footer part; the vertical line fills up from body until footer, although there is only 1 item to display.
I've been trying to use `Autosizing` with anchor the bottom, but doesn't work, either.
@David: do you have it solved, already? Would you mind to share the solution as well, here? Thanks
Unfortunately, using a portal can trade one set of problems for another.
Phil , you are the "BOSS" ..
Man you are soooooo quick.. I always follow your suggestions..
can you please specify, how portal create problem..i am using simple setup..invoices n printing through portal..i just need to print list of invoice for said customer...so I thought portal is great for that..
but I think if its actual invoice printing then taxes and other stuff might create problem..can you please specify it in detail, if possible..????..so I can avoid using portals for those things..
Thanks a lot..
Portals are optimized for data entry not printing. They can be used successfully for printing as long as you respect their limitations:
- You can only print as many portal records as you have rows in your portal. If you have 11 related records and 10 portal rows, one row will not be printed.
- You can set the portal to be very many rows tall and set it to slide up/resize enclosing part to show only the rows used, but note that this would not work for the case here as they want a vertical line extending the length of the page and you still have an upper limit on the number of related records--even if it is very large
- And you can cannot have the individual fields of a portal row slide up/resize to accommodate data that may require more than a single row of text.
All of these issues are avoided with a list view layout based on the portal's table instead of the parent record's table. But we do still have the limitation discussed here. Personally, I'd just do without the vertical lines.
"Regrettably, I don't know of a way to get the "no man's land" between the last record and the footer to show that vertical line."
That "no man's land" is the trailing grand summary. Make it bigger than the page, allow it to break across page boundaries, and discard the remainder of the part.