>Hi Mark, thanks for the quick response.
>
>6.0, I should have said originally.
>StrToFile()--Er, yes, but that almost undoes the convenience. These programs change frequently, as do our customers's minds. Storing them in a table makes for easy updates and I thought, at least, low overhead. What are the ramifications of multiple simultaneous requests for the same report prg if it has to be compiled and run as an fxp each time?

As long as the snippet is compiled to a local folder, you won't have any problem. You can just kill the prg and fxp after the program runs.

You aren't going to get any more low overhead than this approach.