>Interesting! That *does* seem to be what's happening. The only records that are wrapping too early are those where the remainder won't be able to print on the first page. However, my client won't accept that. Is there a way to impose a programmable page break where *I* want it to go, instead of where FoxPro decides to put it itself?
>
>When this database starts being populated with live data, there will be several stretching memo fields in each record, meaning that there could be some real unpredictable results when FoxPro attempts to accomodate the records on the page(s).
>
>>then problem is that once the report writer reaches a certain point (varies), it looks at the rest of the fields that is supposed to print below that. if it can't fit all of the remaining items on what space is left, it moves everything left to the next page.
>>
>>>Thanks for writing!
>>>
>>>"field3" *is* set to FLOAT already. In fact, ALL my fields are set to float. I'm wondering whether I just need to re-create the report from scratch, to see if it will work.
>>>
>>>>try telling field3 and below to float (not fixed to top of report).
>>>>
>>>>>Greetings!
>>>>>
>>>>>I have a relatively simple report layout in VFP3.0 that contains a few
>>>>>memo fields. Each page or two contains the contents of ONE record,
>>>>>with the fields being arranged in order down the page, such as this:
>>>>>
>>>>> field1......
>>>>> field2 (memo)....
>>>>> field3.....
>>>>> ... and so on.
>>>>>
>>>>>What's happening is this: If the memo contents of field2 stretches
>>>>>past a certain point down the page, field3 is started on the next
>>>>>page, even though field3 occupies only ONE line and there is more than
>>>>>adequate room to accomodate it below field2.
>>>>>
>>>>>I cannot find any option settings that keeps this from happening. The
>>>>>wrapping does not happen on every record, but rather ONLY if field2 is
>>>>>stretches past a certain point on the page. This is frustrating,
>>>>>since the first page still has about 5 inches of blank space left
>>>>>over, even though the next field to print occupies one line!
>>>>>
>>>>>What am I overlooking?? Any help would be very appreciated. Thank
>>>>>you!
>>>>>
>>>>>Michael Reynolds

Michael,
I remember a time back when I was working in FP 2.6, and had a similar problem.. I finally just wrote a routine to give me a certain # of lines from the memo field (had to calculate the # of available lines after last memo field) and this allowed me to get the effect I needed..

Thanx!

Tony Miller
Vancouver, Wa