Your version of SAS Management Console must match your SAS server version. For example if your SAS server version is 9.4M4 then your SMC version should be 9.4M4 - it should match right down to maintenance release. ... View more

@tessa_h, I think that @PoulRavn is talking about the layout in the view data window, not the variable lengths and formats on the data set. And, unfortunately I haven't seen such a feature yet. One would wish for something similar to the old good wsave in DMS SAS... ... View more

@Reeza has given you a good explanation.  I would just add that this is another good example of why not to keep "data" in table names/column names.  Table names and variable names are for programming purpose - they are not to store data in.  It makes your life much harder if you are trying to work out what datasetnames are, what column names are.  Have a read where the "data" in the filename is stored to the dataset, and have one dataset for all the data.   ... View more

This is what the first 30 lines of my mru.config look like: <?xml version="1.0" encoding="utf-8" standalone="yes"?><MRU><DNA>&lt;DNA&gt;   &lt;Type&gt;LocalFile&lt;/Type&gt;   &lt;Name&gt;F1.egp&lt;/Name&gt;   &lt;Version&gt;1&lt;/Version&gt;   &lt;Assembly /&gt;   &lt;Factory /&gt;   &lt;FullPath&gt;C:\Users\Username\SAS\F1.egp&lt;/FullPath&gt; &lt;/DNA&gt;</DNA><DNA>&lt;DNA&gt;   &lt;Type&gt;LocalFile&lt;/Type&gt;   &lt;Name&gt;F2.egp&lt;/Name&gt;   &lt;Version&gt;1&lt;/Version&gt;   &lt;Assembly /&gt;   &lt;Factory /&gt;   &lt;FullPath&gt;C:\Users\Username\SAS\F2.egp&lt;/FullPath&gt; &lt;/DNA&gt;</DNA><DNA>&lt;DNA&gt;   &lt;Type&gt;LocalFile&lt;/Type&gt;   &lt;Name&gt;F3.egp&lt;/Name&gt;   &lt;Version&gt;1&lt;/Version&gt;   &lt;Assembly /&gt;   &lt;Factory /&gt;   &lt;FullPath&gt;C:\Users\Username\SAS\F3.egp&lt;/FullPath&gt; &lt;/DNA&gt;</DNA><DNA>&lt;DNA&gt;   &lt;Type&gt;LocalFile&lt;/Type&gt;   &lt;Name&gt;F4.egp&lt;/Name&gt;   &lt;Version&gt;1&lt;/Version&gt;   &lt;Assembly /&gt;   &lt;Factory /&gt;   &lt;FullPath&gt;C:\Users\Username\SAS\F4.egp&lt;/FullPath&gt; &lt;/DNA&gt;</DNA><DNA>&lt;DNA&gt;   &lt;Type&gt;LocalFile&lt;/Type&gt;   &lt;Name&gt;F5.egp&lt;/Name&gt;   I left the first line alone, up to the end of the <MRU> tag. I then removed entries starting with the <DNA> tag, and ending with the </DNA> tag. Note that immediately following the </DNA> tag is the next <DNA> tag.   When I treat the first two entries this way, they disappear from my “previous files” list. Good luck,    Tom ... View more

ods _all_ close; proc print data=sashelp.class;run; or re-direct LOG into an file. proc printto log='c:\temp\temp.log' ; run; ..... Your Code ........ proc printto;run; Xia Keshan Message was edited by: xia keshan ... View more

Look at ODS PROCLABEL to change entry names. Also see if you can use SGPLOT instead of GPLOT, it has the DESCRIPTION= option in the PROC SGPLOT statement to manipulate TOC entries. ... View more

I agree -- it's often overkill to import the entire table, which is how File->Open->OLE DB works.  SAS/ACCESS to OLE DB or ODBC is a better option if you have the modules available.  There is a short primer on this concept here: 26178 - Efficient Data Access using SAS Enterprise Guide Chris ... View more

If you create an Ordered List in SAS Enterprise Guide, the you can add just the specific tasks in a project flow that you want to run, and order them in the order you want to run them in.  See 26177 - Avoid Entropy with the Ordered List Using SAS Enterprise Guide ... View more

Poul, SAS Enterprise Guide finds JMP by looking in the Windows registry for the JMP automation instance, and then falls back to the application associated with JSL files.  If you have 32-bit EG and 64-bit JMP (or vice-versa), it might be that EG is finding one version of JMP before the other.  If you have 32-bit EG you can try to fix it by running this command from a Windows Command Prompt (all on one line): %windir%\SysWow64\reg.exe add HKCR\CLSID\{97BCFCC0-7822-11CF-9E68-0020AF24E9FE}\LocalServer32 /ve /d "C:\Program Files\SAS\JMP\11\jmp.exe /Automation" Double-check the installation location of JMP 11 to make sure the path is correct for your install. Chris ... View more

The resulting dataset may be changed. You get into trouble with the input-dataset (fixed) and appserver. It looks a Eguide design creating objects only be usuable as a one-off project. ... View more