>>>>>Micheal,
>>>>>
>>>>>Re: VFP 3.0 Report wrapping too early
>>>>>
>>>>>I was curious so I made up a test table consisting of 3 fields creatively named field1,field2, and field3, Fields 1& 3 were Character fileds
>>>>>with a length of 10. Field 2 was a memo field.
>>>>>
>>>>>I placed 3 records in the table fields 1 & 3 were set to the record number of the record and field 2 was loaded with a lot of gibberish.
>>>>>I then created a report with the three fileds with all three fields in the detail band. Field1 was the top field, Field2 was just below field1, and field3 was the bottom field. Field 2 was set to stretch and fixed from the top. Field 3 was set to float. I was unable to recreate your problem. The memo record for one record was 10 pages (I got carried away) and the other two records were 1/2 page and 3/4 page. The data was grouped on field1 with a new page on each group.
>>>>>
>>>>>I guess I am trying to understand the problem.
>>>>>
>>>>>A completely unreated observation: When I first Received VFP 3.0 I tried to build an executable and I could not.
>>>>>I called Microsoft (and got through) complained and received a new copy of VFP3. I installed it and was able to build executables.
>>>>>I wrote it off as a production problem.
>>>>
>>>>WOW! Thanks a lot, Ken, for trying to emulate the problem. I think your inability to re-create the trouble (bug??) is that there needs to be more populated fields after your memo field. If field2 (the memo field) is stretches just long enough to prevent the remainder of the fields from being on the same page, FoxPro will cause a page break, EVEN though there is enough room on the page for a few more fields---like about 4 or 5 inches worth, depending on how many fields are left to display.
>>>>
>>>>If YOUR FoxPro works correctly, I think I'll just pay a visit to Microsoft (they're not far from me) and ask for a replacement in person! :)
>>>>
>>>>Thanks again!
>>>>
>>>>Michael Reynolds
>>>
>>>Micheal,
>>>
>>>I increased my test table to 20 fields and ran another report. I got the bug. So I looked over some old reports I have done for clients becuase I have never run into this problem on this type of report. I noticed that by circumstance (or good planning) that my memo fields were at the bottom of the report layout asnd not showing the bug. So I went to my little test report, moved the memo field to the bottom and the erport works fine. All records show on the page.
>>>
>>>If your client will accept the memo field as the last field of a record, it should work.
>>
>>When I took another look at my report, which had a similar problem, I realized that although my memo looks like the last field on the page when it is printed, it isn't really. I have a two page report, run off a cursor which makes separate records for page 1 and 2. The memo has a PRINT WHEN pageno = 2, and all the other fields PRINT WHEN pageno = 1. Even though these other fields don't actually print below the memo, they are below it in the report layout. That must have caused my problem. I was getting blank pages printing after the memo when it exceeded half a page or so. No easy fix for me, I think.
>
>Michael,
> Trying to print a multipage report using Foxpro's report writer is down right hard!! You may want to look at a 3rd party report writer for this.. Maybe FF would handle this?? I would start there and get their demo for VFP.... This will allow you to atleast test it out with your data, and see if it will work.. If nothing else, get on their website and ask them if FF will handle it..
>
>Thanx!
>
>Tony Miller
>Vancouver, Wa

My solution is working, except for the fact that my memo is now limited to one page. If the users become unhappy with that limitation, I'll try to get them to invest in a 3rd party product, as you suggest. By the time that happens, I may be automating Word or Excel for the purpose, anyway.