Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I suspect you have another bug somewhere prior to this statement in your code. Try restarting SAS and executing just those two lines of code and it should work fine, <strong>it worked just fine for me</strong>:</p> <pre><code>%let root = c:\documents and settings\robert.penridge\desktop\mine\sas; %include "&amp;root\lib\work.sas"; </code></pre> <p><strong>EDIT</strong>: This worked for me because I actually added a semicolon. Realised this after @Joe's correct diagnosis of the problem.</p> <p>I created the following folder structure on the desktop:</p> <pre><code>\mine\sas\lib </code></pre> <p>And then put work.sas in there with the following contents:</p> <pre><code>%put blah; </code></pre> <p>When I ran the code the results printed <code>blah</code> just fine with no error messages. In fact I have used code just like this across many versions of SAS and across many operating systems for many years. There's no issue with your code.</p> <p>Contrary to what some of the other answers suggest here, SAS is smart enough to know that the <code>\</code> character can not be part of a macro name so there's no need to explicitly state the end of the macro with the <code>.</code> character.</p> <p>Finally, if you are trying to debug macro code you can also turn on the following options:</p> <pre><code>option mprint mlogic macrogen symbolgen source source2; </code></pre> <p>You can turn them back off like so:</p> <pre><code>option nomprint nomlogic nomacrogen nosymbolgen nosource nosource2; </code></pre> <p>Just be aware that some of these may already be on by default in your SAS environment.</p> <p>In rare circumstances you may also be running into a macro quoting issue. This will happen if you have been using macro functions like <code>%str()</code> <code>%bquote()</code> etc... If this is the case then it can often be resolved by using the <code>%unquote()</code> function around the macro variable that is causing issues. From your code sample it doesn't look like this is the issue but you might have simplified your code for the post. If this were the case then in your situation the code would be changed to look like this:</p> <pre><code>%let root = c:\documents and settings\robert.penridge\desktop\mine\sas; %include "%unquote(&amp;root)\lib\work.sas"; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POUsing LET variable in INCLUDE command in SAS?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRobert Penridge
    1. USRobert Penridge
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODear Sir, are you 100% sure, that the statement "SAS is smart enough to know that the \ character can not be part of a macro name" is true for all encodings configuration? Is SAS that smart?
      singulars
      1. PO
      1. USWojtusJ
    2. COSAS does recognize the end of macro when it is not in A-Za-z0-9_ - that's the default. I disagree on not using terminating . (I think it helps readability) but I agree that this isn't the specific cause of the error posted above, unless there is something not being said by the OP.
      singulars
      1. PO
      1. USJoe
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload