>Hi Nick (this could get confussing :))
>
>
>> Just wondering, why would you need to do it this way? If you read the
>> program in, therefore the source code exists initially. Security reasons?
>
>Main reason is that I want the directory containing the source code to be read-only.

>
>> Anyway, why not store FXP in memo field and then write it on disk, execute
>> and delete it?
>
>I think this would be a major performance hit.


Sure there is some performance hit, but the impact depends on how many times you run this code.
Also, you could add that compiled FXP to the list of your procedure files with SET PROCEDURE TO... ADDITIVE, so it will be open and ready. FXP could be compiled into another temporary folder, not into read-only directory with the source code.


>
>I just feel like there must be a better/cleaner way but at the moment I can't see it.
>
>NickC