To remove the first 4 characters, the syntax for SUBSTR would look like SUBSTR(c_key,5). The 2nd argument determines what position you want to start reading the value, and if there is no 3rd argument, it will read the rest of the value.   17 data a; 18 c_key='hhh-123456789'; 19 run;   NOTE: The data set WORK.A has 1 observations and 1 variables. NOTE: DATA statement used (Total process time): real time 0.01 seconds cpu time 0.00 seconds 20 21 data b; 22 set a; 23 new=substr(c_key,5); 24 put c_key= new=; 25 run;   c_key=hhh-123456789 new=123456789 NOTE: There were 1 observations read from the data set WORK.A. NOTE: The data set WORK.B has 1 observations and 2 variables. NOTE: DATA statement used (Total process time): real time 0.01 seconds cpu time 0.00 seconds ... View more

While it may not have been obvious in Enterprise Guide 7.1 and earlier, all work done was within a project. That was the way Eguide worked before version 8, and why you were able to use the project log when running programs (.sas files). To mimic what you were doing in version 7.1, you can enable the option to automatically open a project file upon startup, and then make sure any programs you open are added to the project:       If you prefer to work only with program files in Eguide 8.1 and not use a project, then another option is to use PROC PRINTTO and write the log out to an external file. You can append the logs by using the MOD function on a FILENAME statement:   filename test 'location_on_server\mylog.txt' MOD; proc printto log=test; run;   As a note, if you use PROC PRINTTO, the enterprise Guide log will be empty. There isn't a way to write the SAS log to both SAS/Eguide and an external file.   ... View more

This may not be the most elegant way, but you can use PROC SQL and query dictionary.columns to get the names of the datasets that contain the CODE variable (and library name if necessary), and also the number of data sets that have the variable, and write those values to macro variables. Then in a macro you can read each one and look for a specific value in the CODE variable. If the data set contains it, capture the data set name and write it out to a final data set.   data x1; input code $; cards; AB1 CD2 EF3 ; run; data x2; input code $; cards; AB2 CD2 EF4 ; run; data x3; input code $; cards; AB1 CD3 EF3 ; run; proc datasets lib=work; delete find final; run;   proc sql; select count(memname) into :cnt from dictionary.columns Where upcase(name) = "CODE"; select memname into :dsets1-:dsets%trim(&cnt) from dictionary.columns Where upcase(name) = "CODE"; select libname into :lib1-:lib%trim(&cnt) from dictionary.columns Where upcase(name) = "CODE"; quit; %macro v_find; %DO i=1 %TO &cnt; DATA find; set &&lib&i...&&dsets&i; if code='CD2' then do; dname="&&dsets&i"; output; end; run; %let dsid=%sysfunc(open(work.find)); %let ret=%sysfunc(attrn(&dsid,any)); %let rc=%sysfunc(close(&dsid)); %if &ret GE 1 %then %do; proc append base=final (keep=dname) data=find force; run; %end; %end;   %mend;   %v_find;   ... View more

data qtr (drop=temp); input Period $; temp=input(trim(left(substr(period,3)))||left(substr(period,1,2)),yyq6.); newdt2=intnx('qtr',temp,0,'end'); format newdt2 ddmmyy10.; cards; Q12022 Q22022 Q32022 Q42022 Q12023 ; run; ... View more

Perhaps you don't have the correct schema value on the LIBNAME statement? You can use the code below to query the database and create a SAS data set with the list of available database tables, which have two-level names. The first level is the schema.   proc sql; connect to odbc (dsn=servername uid=userid pwd=password); create table test as select * from connection to odbc(ODBC::SQLTables); quit ; ... View more

The easiest way is to simply schedule an Enterprise Guide project.  Here is a SAS note that explains further:      56648 - Tips for scheduling a SAS® Enterprise Guide® project ... View more

Doing something similar to the following code should create a data set (WORK.LIST) with two variables, listing the data set containing the variable name you are searching for, and in what library the data set is located. You just need to substitute 'VARNAME' with the actual name of your variable.   proc sql; create table list (keep= libname memname) as select * from dictionary.columns where upcase(name)="VARNAME"; quit; ... View more

This code works for the sample data you provided:   data have; input id name $ score code $; datalines; 1 John 21 ABC 1 John 22 XYZ 1 John 23 ABC 2 Mark 4 XYZ 2 Mark 6 XYZ 2 Mark 5 ABC ; run;   proc sort data=have; by id code score; run;   data want; set have; by id code score; if last.code; run; ... View more

Turning your character date string into a numeric SAS date value with the INPUT function is a much easier option (lot less coding), and then you can apply the YYQw. format to the SAS date value so it displays in the style you want:   data SummaryLookup; input adjudication_dt_id $; cards; 20190105 20210907 20200430 20221231 ; run; proc sql; create table date_test as select adjudication_dt_id, input(adjudication_dt_id, yymmdd8.) as new_dt_id format=yyq6. from SummaryLookup; quit; ... View more

Try this:  In Tools - Options - Data - Performance, change the option to determine which tables are opened when generated to 'No Table'.     ... View more

Another option is to use the Enterprise Guide export GUI method to export a data set to Excel. With the data set open, you would select either Share -> Export or Share -> Export as a Step in Project, and then you can select the windows network location on your PC as the location to save the Excel file. ... View more