>In addition to what Edward says, many frameworks have custom Form.About() method which is supposed to keep some information about form. If you have some notes about how this form works or user README, just add that method to your base form class. You may not comment out the text in the method, but wrap it into TEXT...ENDTEXT.

I think the problem is a little bit more complicated. If I use a property, will be stored in the SCX in the Properties field as Property=Value, so the value I put on cannot be as large as I want. If I use the About() method, how can I access it? I wanna retrieve the the data I put in the SCX when the form is loaded, not at design time!
Maybe if I explain the problem you'll understand me better:
I developed a SCX visual editor in VFP, similar to the native MODIFY FORM editor, but customized to my customer needs. The problem is that if I want to put code in the SCX, I have to compile the form with COMPILE FORM after I save it, wich requires me to run under the VFP environment, not in a runtime VFP exe! That is something my customer want to avoid. My solution (experimental so far) is to use VBScript. I expose some VFP data environment via an VFP API OCX (an OCX compiled with the API libraries, that has access to the pro_ext.h declared functions) and parse VBScripts via Microsoft's Script engine (also JavaScript, the script engine support both without problem). My problem is where do I store the script text? I have to store large amount of text, containing CR/LF and quotas. The User memo field looks perfect, is related to each object of the form and can easily handle large text data. But how can I access it when I'm loading the form? I don't wanna scan the SCX file from disk (wich, by the way, *will* be available, since I'm talking about end-user created forms with my editor, stored on disk files, not inside an APP or EXE).

Any hints?
Best regards,
Remus