This is a common challenge when debugging applications.  To avoid this kind of problem in the future, you might want to consider the SASjs approach - where all source code is managed locally, in a GIT repository, and jobs / services / tests are deployed as self contained units - ie, all dependent macros are 'compiled' into a single program, without any need for SASAUTOS or Catalogs or suchlike.   More info here:  https://sasjs.io/resources/#other-useful-websites ... View more

ı problem solved:    LIBNAME Newlib ODBC NoPrompt="Driver={SQL Server}; Server=xservernamex; Database=xdbnamex; user=; pwd="; ... View more

Would this work as a single pass of WANT if the data step created it as a VIEW? ... View more

It was Risk Management, I found the objects somewhere in the installation folders. ... View more

@Datino wrote: Yeah sorry, it's part of a more complex excercise but I didn't want to ask for the whole solution and figure out some things on my own.   The problem is the one I described in my last post.   There's one ID variable and one last_modification_dt variable. Some IDs have several last modification dates. For each ID with more than one last_modification_dt, I have to find out if the difference between them is less than 7 days, and how many 'less than 7 days diff' are there for each ID.   I thought I would be able to do it with an array but there doesn't seem to be a simple way for me to reference each observation inside the variable in it. You should be able to use DIF() and or RETAIN, though a SQL join is probably easier. If you provide sample data and expected output you'll likely get a solution. ... View more

Hard to tell (this may depend on what parts of out-of-the-box SAS CI functionality and reporting you are using), but this field was clearly not supposed to be used this way.   Response_SK is (or should be) a foreign key to CI_RESPONSE dimension table and that's it.    You can use an existing column EXTERNAL_RESPONSE_INFO_ID1 / ID2 to store IDs for each response record. If you are using an older SAS CI version where these columns were not there, you can just add a new column yourself.          ... View more

data names; input name $ ssn $ invited $; datalines; john 10 n phil 12 n charles 13 n ; data donations; input name $ ssn $ donated; datalines; joe 23 1000 george 18 4599 phil 12 6553 ; proc sql; update names as a set invited='y' where exists(select * from donations where a.nam e=donations.name and a.ssn=donations.ssn); quit; ... View more