How to update a teradata table using SAS access?   I have two teradata tables: Table 1: Id   Col1    Col2 1     x          y 1     a        b 2     x          y 3    g          h 4    x          y 4    a         b   Table 2: ID   Remark    Date 1     complete   02jan2004 1     pending     06jan2004 2     complete    08jan2005 3    pending      08feb2005 3    pending      07mar2005 3   pending      09mar2005   I neeed the remark column with the max of date to be updated to table 1. Suppose if those were sas datasets, the code is pretty easy:   proc sql; select a.*, b.remark from table1 a left join  (select distinct id, remark, max(date) as max_date from table2 group by id; having date=max_date) b on a.id=b.id; quit;   But I my tables are teradate tables, I find the SAS access execute statement pretty challenging. Can anybody help? ... View more

Hello all, any programmatic way to compute the problem perhaps with a SAS function?     Let x be the set of possible outcomes from rolling a dice twice, x = {(a, b) : a, b ∈ {1, 2, 3, 4, 5, 6}}.  Let A be the subset of x given by {(a, b) ∈ x : a + b ≥ 10} and let B be the subset {(a, b) ∈ x : a = 5}.    (a) Write the sets A and B in a new variable    (b) Write A and B in list form (i.e. as a list of elements enclosed in {. . .}).    (c) Write A ∪ B, A ∩ B and A \ B in list form in new variable    (d) write the set x \ A in in a new var. ... View more

I would like to understand how the macro processor looks up the global symbol table when resolving the second %put outside statement. If my understanding is correct, the first %let assigns a value of 1 in the global symbol table, however when forcing the same name as a local within a macro definition, what really happens? Does it create another macro variable with the same name in the local symbol table when a macro variable with the same name exists in the global symbol table? Any chance of overlap or ambiguity here? I would appreciate if somebody can explain the mechanism at length, please and thanks!!!!   Cheers, Charlotte from England   %let variable=1; %macro routine; %put ***** Beginning ROUTINE *****; %local variable; %let variable=2; %put The value of variable inside ROUTINE is &variable; %put ***** Ending ROUTINE *****; %mend routine; %routine %put The value of variable outside ROUTINE is &variable; Submitting these statements writes these lines to the SAS log: ***** Beginning ROUTINE ***** The value of variable inside ROUTINE is 2 ***** Ending ROUTINE ***** The value of variable outside ROUTINE is 1 ... View more