Depends on the os of both environments, if they are the same, i would not expect any problems. ... View more

Just another solution: data want; length v1-v3 $ 1; do _n_ = 1 by 1 until(last.date); set have; by id date notsorted; v1 = coalescec(v1, var1); v2 = coalescec(v2, var2); v3 = coalescec(v3, var3); end; do _n_ = 1 by 1 until(last.date); set have; by id date notsorted; var1 = coalescec(v1, var1); var2 = coalescec(v2, var2); var3 = coalescec(v3, var3); end; drop v1-v3; run; ... View more

Sorry, but i don't understand the problem, too.   I would remove all macro statements and verify that the program does, what it should do. Your macro-variables should not start with an underscore, some automatic variables, like _ClientProjectPath, use the underscore to identify them as automatic variables. So the data step would look like data customer_details; set work.installation; where Contract = 'Y' AND Colour in ('Red', 'Orange', 'Blue') and contract_date_start="01Mar2022"d and contract_date_end="31Aug2022"d; run; Now the export: proc export data= work.customer_details dbms= xlsx file= "PATH/customer_details.xlsx" replace; run; Why do you want a macro at all?   Note: code is untested. ... View more

Untested: proc sort data=have out=sorted nodupkey; by group code; run; data want; set sorted; by group; if not first.group and code = 'B' and lag(code) = 'A'; keep group; run; EDIT: Simplified the code.  ... View more

Remove all macro-code and write it down with normal sas code for at least one case. Than post that code and we see how to generalize it. Moving data into macro variables leads almost always to unnecessary complex code. ... View more

It seems as if you tried to create a table using proc sql without defining at least one variable. Without seeing the log, i can't say anything else. ... View more

From the docs of length: The LENGTH function returns a length in bytes. The KLENGTH function returns a length in a character-based unit. So length returns the correct value in both environments, unfortunately many sas user (including myself) have ignored the fact, that the result depends on the encoding. Our 9.4 environment hast two SASApps, one for latin1 the other one for utf-8.   Are there any other ways to migrate code from SAS9.4 to Viya3.5 without changing all non-K-Functions to K-Functions? Afaik there is no other way. ... View more

How are you using sas? Local installation, SAS on demand, Client-Server-Setup? ... View more

Try proc report: group by student and course, sum for credit and across for n_grade. ... View more

I want to stitch the prescriptions for the SAME drugs for EACH patient together I am sure you have good reasons for this, but except for very few things, your wanted structure is crap. All starts with the problem, that you can't create variables dynamically. You have to know how many obs will be merged before you start to merge them, which is hardly possible.   Here's an ugly attempt to solve the problem, in future posts i except, that you post data in usable form. proc sql noprint; select count_id into :maxCount trimmed from ( select count(id) as count_id from work.have group by id, drug ) having count_id = max(count_id) ; quit; data want; set have(rename=(order_desc = _order_desc)); by id drug; length order_desc1 - order_desc&maxCount. $ 3 first_start last_start last_end 8 sum_days 8 o_count 8 ; retain order_desc: sum_days o_count first_start; array descs order_desc1 - order_desc&maxCount.; format first_start last_start last_end date9.; last_start = lag(start_date); last_end = lag(end_date); if first.drug then do; call missing(of order_desc:); sum_days = days_supp; order_desc1 = _order_desc; o_count = 2; first_start = start_date; end; else do; if (last_start <= start_date <= last_date) or (last_end + 7 > start_date) then do; descs[o_count] = _order_desc; sum_days = sum_days + days_supp; o_count = o_count + 1; end; else do; s = start_date; e = end_date; d = days_supp; start_date = first_start; end_date = last_end; days_supp = sum_days; output; start_date = s; end_date = e; days_supp = d; call missing(of order_desc:); first_start = s; sum_days = days_supp; order_desc1 = _order_desc; end; end; if last.drug then do; start_date = first_start; days_supp = sum_days; output; end; drop s e d first_start last_: sum_days _order_desc o_count; run; ... View more

@yaakov555 wrote: where name contains 'mobile'; This won't match, if name is "Super Mobile Provider". ... View more

I don't understand the problem: "I have tried propcase(tranwrd(ADDR,'Cl','Close')) as ADDR. But this only does one name per time." - Please post the code you have used along with the log. So that we what happens actually.   For data cleaning i would always use a data step, the code is easier to debug. One problem could be caused by the length of the variable addr. Is it long enough to hold the additional chars?   A data step could look this: data want; set have; length addr_expanded $ 100; addr_expanded = tranwrd(addr, 'Rd', 'Road'); addr_expanded = tranwrd(addr_expanded, 'AVE', 'Avenue'); addr_expanded = tranwrd(addr_expanded, 'CL', Close'); run; ... View more

Is t2 a sas dataset or another postgres table? ... View more