>Maybe a .prg would be simpler - just
>
>

>text textmerge to lcPrgtext noshow
>define class <<classname>> as custom
>
><<lcProperties>>
>
><<lcMethods>>
>enddefine
>endtext
>strtofile(lcPrgText, lcPrgFile)
>compile (lcPrgFile)
>

>
>And you get your fxp. But since we don't need to turn this into another "prg vs vcx" thread, whichever works for you is OK.

Dragan,
That was very helpful. I'm going to use the prg method. Simpler is better.
The only benefit to the vcx might be that I would be able to replace smaller sections of the program as the rules change -- rather than ship an entire fxp. But it is probably only marginally better and not worth the complexity of vcx creation. I didn't hear anybody say that there would be a performance benefit from the vcx approach.
Bill