Mike, your analysis is absolutely correct. I used this technique in an (ancient) adaptation of a data-driven report generator -- in that case, it wasn't necessary for the code to be dynamically editable (I wrote a tool to edit the code, compile it and shove the FXP into the table). This technique wouldn't do the job if that capability was a requirement.

Thanks for the clarification.

>>I've been storing compiled FXP files in memo fields since the days of FPD 2.0, extracting them with COPY MEMO, and running them -- never had a problem (at least, until I changed the code and forgot to put the newly compiled FXP in the table :-D --- )
>>Don't know if that's an option here, but if so, it might be another way out...
>
>But this way it is not dynamic, you can't change the code and execute it. BTW, in VFP6 you can use the FileToStr() and StrToFile() functions now :-)