>Last week, some of my colleagues had a wierd problem in one of the modules that we are developping in VFP. In this particular module, a report is being generated of about 4 tables which are part of a relationship. In total this report contains about 5 text fields, a LOGO and 5 memo fields. When printed (on any printer), it prints about 50 pages and then starts skipping pages ang goes through about nearly 6000 pages with blank memos. This happens only if the memo fields are described as stretchable. When we contacted Microsoft, they thought that it might be a bug in VFP and suggested we use VFP 5.0. Has anybody heard about this problem? If so, could you give me some pointers please? Also is there a way in VFP3.0 to print only specific pages (using page no.s like in FOxpro 2.6 for WINDOWS)?
>Thanks.
>
>Sue Mahadevan.

I have used the 3.0 Report Writer with memo fields for over a year without any problems. Have U packed your table and memo file lately? Memo files, like database tables are open to possible corruption, especially over a network. What happens when U preview the report? Does the same problem manifest itself in preview mode. I had some strange problems with a brand X printer one time. Turns out, it was not 100% HP compatible. That was my problem. Maybe U have a similar problem. Is the problem reproducable on a different printer. I don't think U can specify specific pages to print in VFP. U can devise a field to record which records print on which page ahead of time, assuming that U know exactly how many records print per page. I have done this in the past with success in devloping cross-tabluar reports in VFP.

P.S.: I just ran a quick test using three related tables, each with a memo field and everything looks ok. Do U have a problem in the report somewhere... Do U have any function calls within the report? Well, sorry I could not provide further help. htwh Steve