>I want to hide the code, so what I feel is How I can store FXP code into some file and when I required I can extract from it.
>
>I can create run time PRG and call it's function or compile and call that but It may consume some time in IO.
>

If you're willing to pay the cost to extract it at runtime, save the compiled .FXP in a memo field of a .DBF; you can copy it to a file on the user system as needed, and delete it when you're absolutely certain it's no longer needed (you'd best issue a CLEAR PROGRAM to avoid possible side-efects from code caching.

Since an FXP file can be encrypted IAC at compilation, what's the problem with just compiling the file encrypted and leaving it there? To compile MyProc.PRG, strip debug details and encrypt in, issue the command:

COMPILE MyProc.PRG NODEBUG ENCRYPTED

>
>
>
>>Hi Art,
>>
>>- You could either rename the file with a different extension to attempt to concel it
>>
>>- You could compile it into an EXE and call it the same way (set procedure to)
>>
>>Hope this helps~
>>
>>>Hi,
>>>
>>>There are two file, GetBal.FXP & Account.EXE.I want to call FXP file from EXE. I can use command like SET PROCEDURE TO GetBal.FXP ADDITIVE, and call whatever function defined in GetBal.FXP.
>>>
>>>Problem is I don't want to show this FXP file or it's code to user. Also I don't want to include this file into project.
>>>
>>>What are the best possible option for this.
>>>
>>>Thanks in Advance