You know? I just had another thought. I am not sure if this would work for you because I do not know precisely what kind of code we are talking about but I wonder if you could create a "shell" class which would have various methods that you could need. Then, all you would need to do is tell the object which peice of code you want to run and send it the parameters. The code would be compiled into a DLL so that should not be an issue.

This should work if there if you control the code coming through so you can anticipate the various situations you need to handle. If the code is coming from someone else and you have no control over it, it is a different story.

Just to give you a shell example, you could have something like "ADDREC","CUST","111,'MENACHEM BAZIAN','MENACHEM@BAZIANCENTRAL.COM'" in your HTML coming through. Heck, you could even encrypt it if you want. Send that through to your object as:

oMyObject.Execute(paramstring)

and let it figure out what to do based on the parameters you sent through.

Just a thought...

Menachem

>Thanks Nick & Menachem for your thoughts but in this case we really need to do this without writing fxps to disk.
>
>This is for a VFP Web server, the idea being that each .htm file encountered (which could contain VFP code inside <%code delimiters) can be converted into a .prg that returns as it's output the html with all the VFP code interpreted. For best performance it would be best if this were stored as object code and run each time the .htm file is requested.
>
>For security reasons I would very much prefer that neither the .prg nor the .fxp were written into this directory, not even temporarily.
>
>Another problem is that like any Webserver these .htm files are not all going to be in the same place, there will likely be many directories and sub directories containing these.
>
>Regards,
> Nick