Hi Cathy,

Thanks for taking the time to think about my problem.


>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.

I routinely recheck every errorcall with the FPW2.6 version (just to be sure I am not saddled with change requests in the guise of error calls <g>), and working on the same "data" I get less pages in FPW. Also, in FPW it was possible to define reports larger than 1 page: since on that report there were parts which could never be printed together (from the business logic), the report always fits on one page. In VFP I got a "report definition to large for a page (if I remember correctly), but that was easily solved by adding grouping bands for each of the "alternating" report parts.

>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.

Nope, I already doble checked that one. My "dirty mind" trying to enter negative numbers was blocked on the form level - as a last resort I will try entering a negative number directly in the frx.

> Sorry I >couldn't come up with any special tricks for this one.
Well, at least I can tell them, that it is a technical problem, and try to get acceptance either for page brakes "inside" the old groupings or sometimes more pages...

Thanks agaín for your time

Thomas