>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