I've just moved up to FMP 7.0 and Mac OS X.

I have a single-record file, merged to output as a report.

In 5.5 I had to split the merge fields across two layouts because there is a max number of printable pages, and my document is coming in around 25 pages in total.

Somewhere/somehow, I thought FMP 7.0 was bigger and better, and would allow me to print more pages.

I'm wrong aren't I - the same page print limitations apply, don't they? [color:"black"]

I've just moved up to FMP 7.0 and Mac OS X.

I have a single-record file, merged to output as a report.

In 5.5 I had to split the merge fields across two layouts because there is a max number of printable pages, and my document is coming in around 25 pages in total.

Somewhere/somehow, I thought FMP 7.0 was bigger and better, and would allow me to print more pages.

I'm wrong aren't I - the same page print limitations apply, don't they? [color:"black"]

I've just moved up to FMP 7.0 and Mac OS X.

I have a single-record file, merged to output as a report.

In 5.5 I had to split the merge fields across two layouts because there is a max number of printable pages, and my document is coming in around 25 pages in total.

Somewhere/somehow, I thought FMP 7.0 was bigger and better, and would allow me to print more pages.

I'm wrong aren't I - the same page print limitations apply, don't they? [color:"black"]

A layout can extend to about 10 pages in length, no change there. However this 10 page limit applies to each record; it's not often that each record contains more than 10 pages of information.

Records are limited to printing around 10 pages of information. Should this prove to be a problem then the solution is to break up the text into a larger number of records.

Lets say you try to put the Bible into a database and print it. If you manage to fit all the text into one field, say, then put that field onto a layout then you won;t be able to print it, because the record will exceed 10 pages in length.

However if you break the text up and put, say, each verse into a separate record you'll end up with a couple of thousand records. Printing it out will be easy because each record requires less than 10 pages.

A layout can extend to about 10 pages in length, no change there. However this 10 page limit applies to each record; it's not often that each record contains more than 10 pages of information.

Records are limited to printing around 10 pages of information. Should this prove to be a problem then the solution is to break up the text into a larger number of records.

Lets say you try to put the Bible into a database and print it. If you manage to fit all the text into one field, say, then put that field onto a layout then you won;t be able to print it, because the record will exceed 10 pages in length.

However if you break the text up and put, say, each verse into a separate record you'll end up with a couple of thousand records. Printing it out will be easy because each record requires less than 10 pages.

A layout can extend to about 10 pages in length, no change there. However this 10 page limit applies to each record; it's not often that each record contains more than 10 pages of information.

Records are limited to printing around 10 pages of information. Should this prove to be a problem then the solution is to break up the text into a larger number of records.

Lets say you try to put the Bible into a database and print it. If you manage to fit all the text into one field, say, then put that field onto a layout then you won;t be able to print it, because the record will exceed 10 pages in length.

However if you break the text up and put, say, each verse into a separate record you'll end up with a couple of thousand records. Printing it out will be easy because each record requires less than 10 pages.

Thanks for that Vaughan,

Your biblical metaphor makes sense. Unfortunately logic fails me when I begin to consider the actual implications to me.

What you're suggesting (I think) is that I break this down into chunks, and turn the chunks into records?

When it comes to printing are you saying that the records viewed in report mode, can print past page 10, or are you saying that each record would have to be printed as a standalone?

Tim

Thanks for that Vaughan,

Your biblical metaphor makes sense. Unfortunately logic fails me when I begin to consider the actual implications to me.

What you're suggesting (I think) is that I break this down into chunks, and turn the chunks into records?

When it comes to printing are you saying that the records viewed in report mode, can print past page 10, or are you saying that each record would have to be printed as a standalone?

Tim

Thanks for that Vaughan,

Your biblical metaphor makes sense. Unfortunately logic fails me when I begin to consider the actual implications to me.

What you're suggesting (I think) is that I break this down into chunks, and turn the chunks into records?

When it comes to printing are you saying that the records viewed in report mode, can print past page 10, or are you saying that each record would have to be printed as a standalone?

Tim

Create a LIST layout, and show all records... as many pages as you need.

Each record may be limited to 10 pages (the max size of a layout) but a list layout can print any number of records in one print job.

Create a LIST layout, and show all records... as many pages as you need.

Each record may be limited to 10 pages (the max size of a layout) but a list layout can print any number of records in one print job.

Create a LIST layout, and show all records... as many pages as you need.

Each record may be limited to 10 pages (the max size of a layout) but a list layout can print any number of records in one print job.