Canh,

A couple of problems.

1) I asked you to send your report. You sent me (three times, actually) a zipfile containing a portion of your application, complete with .MEM files that pointed to a D:\ folder I don't have and system functions looking at my Windows System directory.

I don't run code that looks like that. Please don't anybody else send it to me.

I don't ever need anything like that to repro a problem. I usually don't even need data.

I am not asking *you* to do the work to fix the FRX so it doesn't need your application to run. I am asking that folks just send me the FRX. I can fix it to run outside your environment, don't worry about that.

I will send you back a zip file constructed from your original FRX that will repro the problem, which uses none of your data except for scoping purposes.

In my revised version of your report, you need to adjust a report variable (test_times) to change the length of the string. The value I will send it with (10) is enough to cause the problem.

You will also find that the problem is probably much worse in my version than in your original, because I used the long string all over the report to deliberately force the stretch.

2) Your report has the potential to cause this issue in all versions of VFP. (In 9, it won't matter whether you SET REPORTB 80 or 90, and it will show the same issue in 7 and 8, I'm pretty sure -- my version does, anyway.)

The reason is that your entire report exists in the page header and your page header stretches to accommodate these stretching text fields. In your case, when the page header stretches, it actually goes beyond the height of a page. It continues to the next page and, because it hasn't finished yet, it is resetting the record # to 1 on each page, with the idea that the detail band has yet to start. Even a scope of NEXT 1 never can get off that record. The result (in my version) is a report appears to go on forever, literally tens of thousands of pages with a one record scope.

I hope this helps you understand what is going on in your report. We can begin to discuss solutions after you look at what you've built here a bit more closely and think about what suitable alternatives there might be. For example, I have no idea why your entire report is in the page header <g>. Perhaps this is not necessary.

Regards,

>L<