07-31-2013 09:41 AM
When developing a large project in E.G. 4.3, I'll often do one off queries using the filter and sort wizard to validate my work. I then go through the project and delete these steps and the generated code as I no longer need them. Is there a way to prevent these steps from being added to the project?
07-31-2013 10:12 AM
Another thought to ponder ...
Maybe the right thing to do is to turn the steps into macros instead of removing them.
Each macro definition would begin with:
%if diagnostics=ON %then %do;
And the entire process flow would begin with %let diagnostics=OFF;
In that way, those steps would not normally run. But if you ever have trouble with debugging down the road, you can just change one line at the beginning:
Then all those steps that never normally execute would suddenly come to life.
07-31-2013 05:20 PM
By way of further explanation, the Process Flow and Process Steps in EG are integral to the way it works. Even if you write just code in EG, it will automatically get added to the Process Flow as a new Process Step when you run the code. There is no way to stop this happening.
One of the few analytical functions that is not added as a Process Step is the Explore Table facility available in EG 5.1 and later. If you have 5.1 then this might be worth checking out but be warned it doesn't work on SAS WORK (temporary) tables or on tables in external databases. This limits its usefulness in my opinion.