A couple of quick tests seem to indicate it has to do with table Memo fields. Putting the data into a memory variable then issuing your TRANSFORM(EVALUATE()) statement worked fine but creating a cursor with a Memo, loading the data into it and issuing the TRANSFORM(EVALUATE()) truncated it to 256 chars. On the surface it would seem to be ( to me ) a bug. But as David mentioned, technically in your case you could probably get away w/o the TRANSFORM().

Bill

>Hi all,
>
>I've built a class which parses HTML pages and replaces special tags within the HTML source with the content of vars and table fields. Worked fine for years, no changes to the classes source code for at least one year. Suddenly customers are complaining about their HTML pages beeing messed up. What happened? We delivered updates compiled with VFP 7 a few weeks ago. I have tracked the problem down to the Parser/Generator module, which contains the following line of code:

lcBufValue = TRANSFORM(EVALUATE(lcEvaluate))

lcEvaluate contains the name of a memory variable or a table field which was parsed out of the HTML source, usually this var/field is a memo which contains severeal hundred/thousand characters of HTML code generated by the app. It seems that within VFP 7 the result of the TRANSFORM() is trimmed to 256 characters - which is the reason for the mess in the rendered HTML page. In the versions before VFP 7 it worked like a charm.
>
>Then I tried this:

lcTransformBuf = EVALUATE(lcEvaluate)
>lcBufValue     = TRANSFORM(lcTransformBuf)
>

and it worked as supposed to!
>
>Is there anything I should know to understand this?
>
>TIA Robert