As I was preparing for a customer introduction to using SAS Enterprise Guide, I asked them to send me all the questions they had regarding the Enterprise Guide usage. It turned out that many of their questions can be answered with a single feature called an autoexec, or automatically executable
What is the best way to organize your SAS work in a SAS Enterprise Guide project? There are no project templates or enforced structure, really, but isn't there a best practice? I don't have a single prescription for the best project organization. I believe that it depends on the nature
AUTOEXEC.SAS wasn't enough for you. Yes, it's a sure-fire way to run SAS statements (such as LIBNAME assignments or macro definitions) whenever you start your SAS session, but you found it has limitations when used in configurations with lots of users who connect with SAS Enterprise Guide. Limitations such as:
A customer posted on the discussion forum that, much his dismay, SAS Enterprise Guide sets the NOFMTERR option automatically when connecting to a SAS session. The FMTERR|NOFMTERR option specifies whether SAS should report an error when you attempt to reference a data column that has a SAS format applied, but
