BookmarkSubscribeRSS Feed
deleted_user
Not applicable
I am having problems while running macros and there is still a code to be corrected. Once I stop the running macro in EG and correct the code it won't run again, but I have to exit EG 4.1 and then start it again so the macro works. Does anyone have a similar problem or know a solution to this. It seems to me that the old macro stays in memory and does not recognize and generates a conflict with the new corrected macro.

Pablo
2 REPLIES 2
Olivier
Pyrite | Level 9
Your guess is correct : SAS stores a list of "bad macros", those who did not run correctly on the first try. Once the macro program is on the list, it can only be removed by closing the SAS session (in your case, exit EG and restart).
BUT there is a way to tell SAS not to check the list when you run a macro :

OPTION MRECALL ;

Just type that at the beginning of the program, and that should solve your problems. (At least I hope so.)

Regards.
Olivier
deleted_user
Not applicable
Dear Olivier,

Thanks a lot for your prompt reply. Life seems to be much easier now.

Kind regards,
Pablo

Ready to join fellow brilliant minds for the SAS Hackathon?

Build your skills. Make connections. Enjoy creative freedom. Maybe change the world. Registration is now open through August 30th. Visit the SAS Hackathon homepage.

Register today!
SAS Enterprise Guide vs. SAS Studio

What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.

Find more tutorials on the SAS Users YouTube channel.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

Discussion stats
  • 2 replies
  • 705 views
  • 0 likes
  • 2 in conversation