Memo Field Truncated in Page Footer

[Auguy]

VFP 9 report. I have a report where there is a memo field in the page footer. This report has worked until I added some text to the memo field. I assumed I had not allocated enough space for the memo. I increased the size dramatically and also marked it as stretchable. It still won't print the full memo. I’ve seen online some references to problems with increasing the size of the memo after the report starts, but this text is fixed for all pages of a report. I didn't think there was a limit to the size of memos in the page footer with VFP 8 or 9. For reference the header band is < 3 inches, detail band < .35, group footer < .2 and the page footer I have now increased to about 2.7. Am I missing something simple, Any ideas?

Auguy
Sylvania/Toledo Ohio

 

[Auguy]

Wait! Hold any responses until I check out the text in the memo field. It appears there might be some strange characters in the text that are affecting the printing.

Auguy
Sylvania/Toledo Ohio

 

[Dan Freeman]

Stretching content in a page footer was an enhancement in VFP8, but I'm still not convinced it's a good idea.

As VFP goes about the business of printing detail lines, it measures the height of the page footer (and possible group headers/footers) before printing each detail band to make sure there's room to print the current detail band before finishing the page.

If the current detail band "goes long" (a UDF for output can do this) while printing it can leave VFP in the position of needing to truncate whatever is in the group(s) or page footer. It can't go back and "unprint".

The RW gives us a ton of ammunition to shoot ourselves in the foot. Unfortunately, we tend to use all of it. <g> (Been there, done that. Will again.)

 

[GriffMG]

The VFP report generator is a work of art and I never cease to be amazed by how well it works.

BUT

It's not unbeatable.

If you need variable size details, groups and headers and footers you need to treat it gently.

Try to find a way to put your narrative fields into a cursor that perhaps can provide VFP with something a bit more predictable to process. One record per line in the report.


So, if there is a novel in the detail, who cares and if there is a novel in the summary likewise.

Bit harder, but worth it

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[Auguy]

Thanks guys. I believe there is something strange in the text I was given and pasted into the memo field. If I replace it with other text of equal length it seems to work fine. In fact when I just replaced it with all upper case of the same text and it worked fine???? If I don't find the problem soon I will try and combine the cursor with them memo field into the mnain report cursor and see if that makes a difference. I did look at the ascii codes in the memo field text and they looked OK. I may have to look again.

Auguy
Sylvania/Toledo Ohio

 

[Dan Freeman]

Huh. Where did this data originate? Did it come from another OS?

If Replace thefield with Upper(thefield) works, I wonder if you could just replace with Transform(thefield) instead?

Transform() can often be the great equalizer.

 

[Auguy]

Thanks Dan. I just tried that with no luck. The text is only 8-10 lines on the report. I'm just going to re-type it, wasted too much time already. Thnaks again to all who responded.

Auguy
Sylvania/Toledo Ohio