Thanks Tom. I suppose I was a bit vague, probably because I have already thought of a few acceptable solutions, I think I am just searching for the best solution and/or a best practice to follow. Here is a few details, any input you have would be appreciated: I have a process flow devoted to general macros that I have written and want available to use in the project. Here are some options I came up with: 1) Make that process flow an "autoexec" process and it will run every time the project is opened. The only downside is that the programs containing the macros would take 10-20 seconds to run every time the project is opened--not a big deal, so this may be the best solution. 2) "Publish" that process flow code by exporting all the code in that process flow to a SAS program. Then, I could either "%include" that SAS program (if it is located outside of the project) or simply copy/paste that "Published" code into the process flow where I would like to call it. The advantage to this method is that it shortens the amount of time needed to run the code and there is nothing running at start up, but the downside is that it requires an extra step. 3) Somehow add these macros into a personal library that will allow them to be available in all my SAS EG projects. The downside to this is that other users would need to have access to these, so this doesn't really solve my problem I suppose. 4) Somehow "%include" the SAS programs which contain my macros. I would like to do something like this, but I think "%include" only works for external SAS programs outside of the EG project. I suppose I am just curious how other SAS developers handle these types of situations. I would love to hear your input, even though it might seem like a silly question. Thanks again!
... View more