Thanks for all the replies. I was able to get it working by changing the following: %macro test; %do date = &min_date %to &max_date; ... View more

I am calling the macro. The only message the log gives me is "Remote submit to Server complete". I'm not getting any errors, etc. It's a little frustrating. I'm open to other solutions. I'm not totally comfortable with macros so I went with what i thought was easiest for me (compliments of the Macro 1 course I took recently). ... View more

I always forget about being able to do multiple "into :'. Thanks for the reminder. I've changed my program to the following but I still can't get it to work. I don't get an error message or anything: proc sql noprint;   select        min(PERIOD_DT) format = date9.,        max(PERIOD_DT)format = date9.             into: min_date, : max_date   from Zwork.period_Dates;   quit; options mlogic mprint; %macro test (first=&min_date, last=&max_date); %do date = &first %to &last; data work.table_&date; set zwork.Emp_History1; if PERIOD_DT in ("&date"d); run; proc export data = work.table_&date outfile = "W:\_TD9756_WAPPRIB00001040_\test.xlsx" DBMS = EXCEL replace; sheet = table_&date; run; %end; %mend test; ... View more

Thanks for the assistance billfish. Arthur, a list is fine. Thanks! ... View more

Thanks all for the many replies. The reason I require the data to be separated is due to how it needs to be processed. The HIST data, as you might guess, is historical data. It needs to be added chronologically by period_date to an Oracle table. The existing macro for current data is as follows: %macro ImportData(dir2=); %let X = %sysfunc(fileexist(&dir2)); %put &X; %if &X = 0 %then %do;   %put ERROR: File Missing. Contact Department;   %goto exit;   %end;   %else %do;   PROC IMPORT   OUT = Employee   DATAFILE = &dir2   DBMS = xlsx Replace;   SHEET = "Test";   GETNAMES = YES;   PROC SQL;   DELETE FROM odbc AMM.AMM_Table;   PROC SQL;   INSERT INTO odbcAMM.AMM_Table   (sasdatefmt =  (   PERIOD_DT = 'MMDDYY10.',   ACTION_DT = 'MMDDYY10.',   EFFECTIVE_DT = 'MMDDYY10.',   TERM_DT = 'MMDDYY10.',   Load_DATE = 'MMDDYY10.'  )  )   Select   MANY VARIABLES.....   FROM Employee;   PROC SQL;   connect to odbc(dsn = &dsnName);   execute (call AMM.UPSERT_Table()) by odbc;   %end; %exit: %mend; %ImportData(dir2= file location); Due to the logic in the call procedure [AMM.UPSERT_Table], I need to add the HIST data by period, chronologically. I won't go into the details of that but creating a macro to take the HIST data and loop through the period_dates so that I can fit it into the existing macro would save me a lot of time.That's my overall plan. If I can not figure out a way to do that I will parse out the data in the HIST table period_date by period_date and run it through this macro a section at a time. It's less elegant for sure, but would still achieve my objective. ... View more

I need to loop the data for each period_date through an existing macro, chronologically. I'm certain it's possible to do without breaking the data into chunks by just using the HIST table but I'm not familiar enough with how to write the logic to do it and haven't had much success researching it online. I figured if i had an example of breaking it out into separate datasets I could adapt that to my needs. ... View more

Each data set would contain all the values from the HIST table where the period_dates are equal. For example the output of period_date  03/21/2014 could have 5345 rows (and associated columns), period_date 04/04/2014 could have 1255 rows (and associated columns), etc. Like if I was to write data EXAMPLE; set HIST; if period_date = 03/21/2014; run; ... View more

The period dates are MMDDYYYYs10. format. Example: 03/21/2014 04/04/2014 07/18/2014 ... View more