>>Also, are there any other special considerations I should keep in mind when developing my app which will eventually become an EXE? > >The biggest limitation I found is that you can't compile from an EXE (e.g. you must have all the code compiled at runtime). > >Vlad Have you tried CodeBlck? I personally don't have much experience with it, but I think it handles this. Here is an excerpt from the comments : * If code were all simple "in-line" code (no SCAN, DO, etc.),
* it is easy to run uncompiled by simply storing each line to
* a memory variable and then macro substituting each line.
*
* Thus, we adopt that approach, but when we encounter any control
* structure, we capture the actual code block within the structure,
* create an artificial simulation of the structure, and pass the
* internal code block recursively to this same routine. Nesting
* is handled automatically by this approach.
* Calling Examples:
* 1) Allow direct typing of code to run:
* DO CodeBlck
* 2) Run the code contained in memo field "TheCode":
* DO CodeBlck WITH TheCode
* 3) Same as 2, but allow review/edit first:
* DO CodeBlck WITH TheCode, .f., .T.
* 4) Run the code found in file "TESTRUN.PRG":
* DO CodeBlck WITH "TESTRUN.PRG", .T.
* 5) Same as 4, but allow user to review/edit:
* DO CodeBlck WITH "TESTRUN.PRG", .T., .T.
* [NOTE: The file doesn't get changed.] Greg