@BrahmanandaRao wrote: data ds; set sashelp.cars; if Make='volkswagan' then call symput("Status",'Available'); else call symput("Status",'Not Avaialable'); run; %put &Status.; it shows wrong  output And just what should be the right output??? I get "Not Avaialable"  (your spelling not mine) with the above code. Since this leaves the STATUS as of the very last record in the input data set are you sure that is what you wanted? The last make in the data set is Volvo so even without the incorrect spelling of "volkswagen" you will never get 'Available' as a result. ... View more

I have modified my code so that it handles properly the case where A is prescribed twice on a day, or B is prescribed twice on a day (or both! 😊 )   data long; set have; do date=start_taking_date to last_taking_date by 1; output; end; run; proc freq data=long; tables id*drug*date/noprint out=frequencies; run; data long1; merge frequencies(where=(drug='A') rename=(count=countA)) frequencies(where=(drug='B') rename=(count=countB)); by id date; retain overlap_first_date; both_drugs=(countA>=1 and countB>=1); prev_both_drugs=lag(both_drugs); prev_id=lag(id); if first.id then prev_both_drugs=0; if prev_both_drugs=0 and both_drugs=1 and (first.id or id=prev_id) then overlap_first_date=date; if prev_both_drugs=1 and both_drugs=0 and id=prev_id then do; overlap_end_date=date-1; delta=overlap_end_date-overlap_first_date; output; end; format overlap: yymmdd10.; drop drug percent prev: countA countB date; run;    ... View more

@ScottBass,    I wonder if EG can be set up such that common contractions (don't, won't, can't, etc.) are automatically converted to their non-contraction form (do not, will not, cannot, etc.).  This might be something along the lines of what @ChrisHemedinger wrote about in the third item of this blog post:  https://blogs.sas.com/content/sasdummy/2017/07/03/sas-program-editor-tricks/.  I mean it stands to reason that the power of the SAS EG editor ought to be able to help us out here, right?   Jim ... View more

@TomKari wrote: Hi, Scott   Yes, you've definitely poked one of the sore spots in Enterprise Guide. Much of what you say is correct, but I differ with a couple of your opinions:   As an Enterprise Guide user since Version 2, I give you my solemn assurance that the STOP functionality works INFINITELY better than it did back then!   With regards to SQL Server tools, it's not surprising that they work better on jobs connecting to SQL Server...they're written by the same company! How well do SSMS and SSDT work against Oracle data sources, or Greenplum, or Hadoop, or SAS datasets? You're comparing apples to oranges on this one, I'm afraid. I don't know of any products that interoperate with as many data sources as SAS.   Tom Hi Tom,   I disagree with your analogy.   I compared SSMS - SQL Server, both written by Microsoft.  Stop processing works.   EG - SAS Server, both written by SAS Institute.  Stop processing doesn't work.   SAS's ability to work with other heterogeneous data sources is a separate discussion, not relevant to this subject. ... View more

Hi Brad,   I was hoping someone from SAS might chime in on this issue but alas... I never got a fix, workaround, or explanation for this issue.   One kludge is to send a message to the output window via select.   The SAS invocation would look something like this:   proc sql; connect using foo; * where foo is an ODBC libref ; select * from connection to foo ( EXEC dbo.spMyStoredProcedure ); quit; And in your stored procedure: IF @SOME_ERROR THEN BEGIN SELECT 'line 1' AS message UNION SELECT 'line 2' UNION SELECT 'line 3' END   You can't return multiple selects, so your code needs to create one select result per logic branch.   I use this technique in some of my stored procedures.  My error processing looks like:   BEGIN CATCH IF (@@trancount > 0) BEGIN ROLLBACK TRANSACTION; PRINT 'Transaction failed, all changes reversed.'; /* This only prints in SSMS, not SAS */ END SELECT ERROR_NUMBER() AS ErrorNumber /* But this prints to the SAS output window in EG */ ,ERROR_SEVERITY() AS ErrorSeverity ,ERROR_STATE() AS ErrorState ,ERROR_PROCEDURE() AS ErrorProcedure ,ERROR_LINE() AS ErrorLine ,ERROR_MESSAGE() AS ErrorMessage ; SET @RC = -1; RETURN @RC; END CATCH HTH... ... View more

You are absolutely right. In this particular case, though, it would not be of consequence, as the subsetting if lets only observations through where a value is found. But I will edit my post, as the other ("left join") hashes would suffer from this effect. ... View more

@ScottBass  - In your EG version the option to limit output datasets is probably this: ... View more

Yes, good point.   I use EG with a local server instance, so I sometimes forget to separate the functions. Also, I was so surpised that there is a "sound" routine that all other thoughts were scattered to the winds. Who the heck put THAT in SAS?   I must admit, I am amused by the thought of a server in a computer room starting to play tunes...maybe use a grid, and have it switch from server to server, so the server room staff can't chase it down?   Tom ... View more

Just thinking: If it's only for checking then couldn't you just do a search in project.xml? For SAS8.2 the tag appears to be ActionOnError. I would assume it's the same in older EG versions.   And adding to above: Using Notepad++ you could do a Find All as this gives you the number of hits and would let you know quickly if there is a program with another specific setting.  Having done a quick inspection of the project.xml: If looks like changes to the default get set as override (same tag but different place in the xml). So eventually search for a string <tag>text ... View more