topic Re: SAS EG project : Advantages and disadvantages in SAS Programming

SAS EG project : Advantages and disadvantages

LineMoon — Sun, 08 Jan 2017 11:44:35 GMT

Hello expert,

Please, I would like to know more about the advantages and disadvantages of sas EG projet in general ?

In particular, what's the advantages and disadvantages of SAS EG Project versus " macro -program"

For the same project : Pr1

> first Method : using only sas macro-program %main_project ( this one call other sas macro pograms)

> second method : create a sas EG project contains ( %main_project and the others macro-programs)

Thank you

Re: SAS EG project : Advantages and disadvantages

LinusH — Sun, 08 Jan 2017 15:31:32 GMT

It's very little to go on here to give such a design suggestion.
If you can't describe the business issue and constraints, I suggest that you try both me gods and evaluate after a period (which need criterias, which should be based on - you've guessed it: requirements and constraints).

Re: SAS EG project : Advantages and disadvantages

LineMoon — Sun, 08 Jan 2017 18:36:23 GMT

In the first time, we can forget the business issue.

Re: SAS EG project : Advantages and disadvantages

SASKiwi — Sun, 08 Jan 2017 19:45:13 GMT

Macro programs require hand coding. I can't see any advantage in putting just manual code into EG projects. The whole point of an EG project is use of the automated tasks.

Re: SAS EG project : Advantages and disadvantages

Patrick — Sun, 08 Jan 2017 20:30:41 GMT

I guess what to go for depends on the use case as well as personal preference.

If the macros get used in multiple projects then I'd store them in a folder which is part of the SAS Autocall facility and though would keep the code external to the project. But I also like to keep as much of the code used within a project so if these macro programs are only used in this specific project then I'd keep the code in the project.

What I normally avoid is to store code externally if only used in one project as this only adds the need for %include statements with path names in it which can add quite a bit of work when migrating EG project to another environment. You would also have to come up with some naming convention or folder structure in order to avoid overriding an external .sas file with a same named object from another EG project. ...but then may-be there is some versioning requirement and you want to check in your code as .sas files ...so "what's the right design decision" depends on requirements and constraints.

Re: SAS EG project : Advantages and disadvantages

LineMoon — Sun, 08 Jan 2017 22:31:36 GMT

@all:thank you all.

@Patrick :

as you said "But I also like to keep as much of the code used within a project so if these macro programs are only used in this specific project then I'd keep the code in the project."

In this case , If I have a macro-programs : P1.sas, ..................., Pn.sas in folder /Test and I add them in SAS EG Project Pr.egp.

In this case , I will store the programs in two places : /test and Pr.egp ? in this case, autocall is better ?

Re: SAS EG project : Advantages and disadvantages

Patrick — Mon, 09 Jan 2017 00:20:22 GMT

@LineMoon In this case , I will store the projects in two places

I wouldn't create copies of EG projects as then you'll have to keep all these copies in sync.

One of my main considerations for design decisions is maintenance and I certainly would avoid to have multiple active versions of the same code/EG project.

Re: SAS EG project : Advantages and disadvantages

LineMoon — Sun, 08 Jan 2017 22:33:05 GMT

sorry, I want to say

I will store the same programs in two places ?

Re: SAS EG project : Advantages and disadvantages

Reeza — Sun, 08 Jan 2017 22:55:16 GMT

EG allows you to visualize a project/program flow, if done in an organized fashion with a systemic naming and comments method.

Code will not allow you see the relationships unless you trace out the programs. The SAS programs can still exist internally as in step 1.

Re: SAS EG project : Advantages and disadvantages

Reeza — Mon, 09 Jan 2017 00:28:27 GMT

At the end of the day it comes down to personal preferences. Unless your company dictates a method.

I would create a small project in each method and you'll get a feel for what works for you.

Look at EG features you don't have in Base, diagrams, multiple process flows, colour coding, prompts, links to Git etc and decide what you need and want.