I have a a bizarre idea. Perhaps you can have the FXPs on disk but just mark them as readonly and even hidden (so they would not show). I will assume that a DO will not work on a hidden file (I would have to test that but I am on a machine that does not have vfp on it) but you could always reset the hidden attribute, execute the code and reset it again when done.

Menachem

>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.
>
>I just feel like there must be a better/cleaner way but at the moment I can't see it.
>
>NickC