Thanks for the clarification. Now I think I understand what you are dealing with.

You are correct in that before printing a band, VFP checks to see if there is enough room to print the ENTIRE band. It does not look at the Print When logic when it is making this determination. I don't know of any way to get around this. I'm also a little perplexed that you said it worked in a previous version of FoxPro because I think this same logic has existed for quite some time.

The only suggestion I have is to double-check each Group definition. There is a setting that says "New page if less than ____". If you have a number entered into this, VFP checks to see if at least this much room is left before printing the group at the bottom of the page. Maybe there's a high number sitting in one or more of the group definitions that you have.

Other than this .. I don't have any other suggestions for you. Sorry I couldn't come up with any special tricks for this one.

Cathy



>Hi Cathy,
>
>>If all the data is sitting in a huge array instead of records in a table or >cursor, how are you doing "groups" in the VFP Report Writer??
>
>There is 1 "actual" record.
>The detail band of the report is empty, but the frx is processed for this singular record.
>
>Since there is one record, all the different group headers above the detail band are processed as well, for that singular record. (trying to move the report fields to the group footer was a desparate move and failed, as I feared).
>
>This (dummy) record then gets a 1 to 4 page report for all the options / data entered for one car insurance police by way processing all those group bands. (I "inherited" this program about 20 month's ago: Not everything is done the way I'ld design it, and filling those array's is something I left alone for the moment: I had to clean out "a few other areas" with calculating errors first <g>).
>
>I guess this approach was choosen since everything is based on array handling as a way to separate the previously saved table record and "current changes", since buffering was not available in 2.6 and gather/scatter memvar could be errorprone if working with tablefields which sometimes have the same name, but are in different tables (sometimes even with different data types).
>
>I do hope that I haven't mixed up terminology, since I am translating from the german VFP. With "groups" I mean the bands which you can optionally
>insert between the page header and the detail band ("Gruppenkopf") and between the detail band and the page footer ("Gruppenfuss"). It's (in the german version) the second item of the reports menu ("Datengruppierung...")
>which opens the form in which you add / change the optional "grouping bands".
>
>If you are interested, i can mail you example frx/frt's as well as screenshots... (wringing my hands above the keyboard)
>
>Regards and Thanks for your interest
>
>Thomas