A while ago I grumbled about not being able to print more than <however
many records I could squeeze into my portal> at the same time and was
told that no, I can't scroll down to print the next batch.

The solution that was generally favoured - go to related records and
print from the other file - is not practical for several reasons; I did
have a play around with it, but had to give up on it.

(I'm still not certain why the 'go to related records' scriptstep was
playing up on me - it works in some of my files but not in others.
Bleh.)

The solution I've got now is to print, go to Portal Rows 1-12 and
remove the association, and print again, and when I'm done, to relookup
the association and thus restore everything.

Maybe not the best solution, but it works.

Catja wrote on (9/30/2005):

How about splitting it among several portals on duplicate layouts?

Assuming 36 records:

Layout 1 has the portal defined to show records starting at 1.

Layout 2 has the portal defined to show records starting at 13.

Layout 3 has the portal defined to show records starting at 25.

etc etc

Script printing each in sequence.

Matt





--

Catja Pafort wrote on (10/2/2005):

In Portal Setup, you specify the initial row and the number of rows you
want displayed. Default is 1.

For the first portal initial row is 1.

Second portal initial row is 13, etc.

Matt

--

Matt Wills wrote on (10/2/2005):

In each succesive layout, go to the last row in the portal and test for
not IsEmpty in a field.

Matt

--