Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
TRANSFORM(EVALUATE()) changed in VFP 7?
Message
From
13/02/2002 13:07:03
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Other
Title:
TRANSFORM(EVALUATE()) changed in VFP 7?
Miscellaneous
Thread ID:
00619604
Message ID:
00619604
Views:
87
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
I've acquired quite a taste for a well-made mistake... [Fiona Apple]
Next
Reply
Map
View

Click here to load this message in the networking platform