Razzak: Thank you for your detailed response.
I'll play with these, and very likely find a fit. Once I study up, I may contact you with a case for 'on the fly' migration of edits from a $$$ file to an RMD file opened within RBEdit (Case #3); to eliminate the 'back and forth' within a TRACE session. Laziness, as a spur to great software creation. Really appreciate the tool as is. Bruce -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of A. Razzak Memon Sent: Thursday, February 05, 2015 9:56 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Saving Changes within TRACE At 12:20 PM 2/5/2015, Bruce A. Chitiea wrote: >While tracing an RMD file within RBEdit, responding 'YES' to editing an >error displayed within the $$$ file, I can edit the error and save the >$$$ file. > >But this change doesn't 'ripple back' to the original RMD file, open in >RBEdit. > >Is this a 'SAVE AS' situation, or is there a way to migrate the change >back to the original RMD; and continue with TRACING? Part II .... Bruce, Try the following steps to actually understand different flavors of TRACE. 01. Database Explorer | Command Files | Select the command file ... Right-Click | Trace File ... This approach will TRACE the selected file and let you update the "same file". No scratch .$$$ file is created. 02. At the R> Prompt ... SET TRACE ON RUN commandfile.RMD This approach will run the file under TRACE and let you update the "same file". No scratch .$$$ file is created. 03. At the R> Prompt ... SET TRACE ON RBEDIT commandfile.RMD While using RBEDIT ... click on the [Run] (Ctrl+F9) button This approach will create an scratch .$$$ file. Once an "Error" message is displayed, clicking on the [Yes] button defaults to the contents of .$$$ tab. However, if you look closely, there is a tab with the original file name next to the .$$$ on the left which you will have to click on, to update whatever the "error" message is all about, referring to the exact line number, etc. Very Best R:egards, Razzak
