Roger;
Essentially, you have two ways to go with this, depending upon how your form
is designed. Given that you can show n-records in a row, I assume that the
records do not contain many columns (fields).
Method 1: Write a module to prepass the table, reading groups of n-records,
assembling them into new individual rows, n-records wide, and writing them
out to a temporary table. Use the temporary table as the record source for
your form. If your form works in continuous record mode, this is the way to
go. You'll need to find a place to run this procedure before the records
are displayed. Perhaps in the OnClick procedure of the command button that
opens the form.
Method 2: Assuming that your form works in current record mode (or at least
looks like it does)...
Do not bind your form to a record source, leave it unbound. Create your own
record navigation command buttons. Write a subroutine that reads the next
n-records (or the previous n-records) and loads them into your form text
boxes depending upon which navigation button is clicked. Run these routines
from the OnClick event of the navigation buttons. Hide the nav buttons
provided by Access.
I guess using a recordsetClone might not be useful in the above methods. If
you wanted to dynamically add text box controls to your form to accommodate
the records, the recordsetClone approach would work. But that would be a
third method which is more complex than the above two.
I know you were hoping for an easy setting way to accomplish this, but I'm
not aware of any such thing. However, these design approaches will get you
where you need to go.
-Jim
Roger said:
Thanks Jim. But I'm not understanding what you're saying. So I create a
copy of the records, and then let the module move them around? I don't
understand how that will change the placement of the text boxes in the
subform.
