Thanks George. I've not had a chance to test it yet. Could be days. I'll get back to you with my results. Thanks.
Daniel

>>George,
>> This is very cool. Thanks. It's way farther than I've gotten.
>>
>Hi Daniel,
>
>First, I have to give credit to "Gonzo" John Koziol for some of what follows. John reminded me privately of an old command that these days is one of those things is included only for backward compatibility: DOHISTORY. If you SET DOHISTORY ON, lines of program code appear in the command window. After doing some, admittedly lightweight, checking, it seems to work fine in FPW. In other words, if you SET DOHISTORY ON, then run the text file (via DO), the contents appear (and stay) in the command window.
>
>One thing to be aware of is the behavior of the various MODIFY commands. Program execution will stop until the editing window is closed, unless the NOWAIT clause is added. Of course, MODIFY STRUCTURE doesn't apply here because of the modal dialog that appears.
>
>So I'd suggest that my program that captured the command window into a text file be modified so that NOWAIT was appended to any line that began with "MODI".
>
>What I'd also suggest is a startup program that would be run automatically by the COMMAND= setting in config.fpw. In the startup program, I'd set the library to foxtools, set ON SHUTDOWN to the progam to capture the command window (you'll have to remember to reset it in any applications you have that use the command). Then, issue SET DOHISTORY ON, do the command.txt file, and restore DOHISTORY to OFF.
>
>Lastly, thanks to "Gonzo" John for the DOHISTORY idea.
>
>hth