Fred, I agree with you in priciple, I just find that in a data driven world, it is easier to have a table ( specialstuff ) where I keep a task list on a user or site basis.

To allow minor changes, I use the text file, so the line in text might be

DO scanorder.fxp with (parameter list unique to customer and date )
DO scanpayroll.fxp with (parameter list unique to customer and date )


The reason I don't immediately execute the program is that the data wll change, and I have to complete one set of tasks before allowing the second to change the data, but the first pass has to build the parameters, and since each client is just a bit different, I don't want to hard code it into the program!

I quite agree that it doesn't work for complex tasks, but, as an example, in an on error routine, you need to BOTH set up a recovery routine AND document the error before the recovery erases the data. Since I can append to a text file without moving record pointers, selects, current program line, etc, I can generate a repair program on the fly without losing my data environment!

Theoretically, I could rename my text file to a .prg, but that caused problems when the program "escaped" !

Anyway, nice to know SP3 has added that feature, one question though, is SP3 automatically distributed with new compiles or do you have to install it at every runtime site ?

thx

Mike