Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Max size of report (frx) variables

Status
Not open for further replies.

jjjt

Technical User
Sep 15, 2002
34
GB
My table contains a memo field that stores data that can run to some considerable size. I want to print this information on a report and there is no problem setting up a field that references the memo - the data will print correctly.

However, I need to do some preprocessing before printing which means I have to store the contents of the memo field to a report variable. As soon as I do this the data is truncated - it looks like the maximum number of chars that can be stored is 256.

Can anybody confirm this, and is there any other type of report variable I can use that can store more than 256 characters?

Thanks in advance.
 
Hi

Instead of to a report variable, if you can hold it in a memory variable by using the command..

SCATTER MEMVAR MEMO..
and then.. process the m.MemoField, the contents will be available. You can then process and print this m.memoField in your report.

If you find that the memory field scattered is not available in the report, for any reason, since the m.MemoField is local to the calling method or event, then..
you can
SCATTER MEMO NAME oMyTable
oMyTable.MemoField will be available in the report which you can modify and use.

:)


____________________________________________
ramani - (Subramanian.G) :)
When you ask VFP questions, please add VFP version.
 
Ramani, thanks for your advice. It would be better if we could process the memo contents in the code, but I'm trying to get a solution for somebody who only has access to the report writer functionality and is therefore restricted to report variables. The only thing that I can think of is to set up a number of report variables and store a segment of the memo field to each. Of course, this only makes the problem less likely to occur, it does not eradicate it completely, since the contents of the memo field might still exceed the capacity of the variables in extreme cases.

(By the way, we use VFP7)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top