Thanks @SASKiwi. But, is there any link or testcenter to test this function, for free ?   ... View more

Hi mate,   First you need to understand how your data is getting in your dataset. This is why you use input statement, you are going to input your data into your dataset. The colon ( : ) modifier enables you to read nonstandard data values and character values that are longer than eight characters, but which contain no embedded blanks. The :  indicates that values are read until a blank (or other delimiter) is encountered, and then an informat is applied. If an informat for reading character values is specified, the w value specifies the variable's length, overriding the default length.   In order to read these values, you can modify list input with the colon ( : ) modifier, followed by the COMMAw.d informat, as shown in the program below. Notice that the COMMAw.dinformat does not specify a w value.   Remember that list input reads each value until the next blank is detected. The default length of numeric variables is 8, so you don't need to specify a w value to indicate the length of a numeric variable.   This is different from using a numeric informat with formatted input. In that case, you must specify a w value in order to indicate the number of columns to be read.     Reading Nonstandard Values and That Mysterious Colon ( : )   Hope this helps. ... View more

PROC IMPORT DATAFILE="/path/test.xls" OUT = FIRSTSTREAM DBMS=XLS REPLACE; SHEET="Sheet1"; GETNAMES=YES; DATAROW=3; RUN; DATA HAVE; SET FIRSTSTREAM; X = _N_; RUN; PROC SQL; SELECT X+2 INTO: FIRSTLINE FROM HAVE WHERE TABLE1 = ""; SELECT MAX(X) INTO: LASTLINE FROM HAVE; QUIT; PROC IMPORT DATAFILE="/path/test.xls" OUT = UPSTREAM DBMS=XLS REPLACE; SHEET="Sheet1"; GETNAMES=YES; DATAROW=2; RANGE="Sheet1$A1:E&FIRSTLINE."; RUN; PROC IMPORT DATAFILE="/path/test.xls" OUT = DOWNSTREAM DBMS=XLS REPLACE; SHEET="Sheet1"; GETNAMES=YES; DATAROW=2; RANGE="Sheet1$A&FIRSTLINE.:E&LASTLINE."; RUN; This code do exactly what you need, and you don't need to specify which one is the line to breakup the tables. You only have to change the where clause in proc sql.   Hope this helps ... View more

Ok, I changed to use macro to get the values and separate the datasets:   PROC IMPORT DATAFILE="/path/test.xls" OUT = FIRSTSTREAM DBMS=XLS REPLACE; SHEET="Sheet1"; GETNAMES=YES; DATAROW=3; RUN; DATA HAVE; SET FIRSTSTREAM; X = _N_; RUN; PROC SQL; SELECT X+2 INTO: FIRSTLINE FROM HAVE WHERE TABLE1 = ""; SELECT MAX(X) INTO: LASTLINE FROM HAVE; QUIT; PROC IMPORT DATAFILE="/path/test.xls" OUT = UPSTREAM DBMS=XLS REPLACE; SHEET="Sheet1"; GETNAMES=YES; DATAROW=2; RANGE="Sheet1$A1:E&FIRSTLINE."; RUN; PROC IMPORT DATAFILE="/path/test.xls" OUT = DOWNSTREAM DBMS=XLS REPLACE; SHEET="Sheet1"; GETNAMES=YES; DATAROW=2; RANGE="Sheet1$A&FIRSTLINE.:E&LASTLINE."; RUN; ... View more

Hi mate, I've never try this but checkout this Embed images in a PROC REPORT table There is a code and you can try yourself.   Hope this helps  ... View more

Hi mate,   This code works as you need:  Use range option to specify the range cells and get the first table and the second, the following example i've made:   TABLE1         COL1 COL2 COL3 COL4 COL5 A B C D E A B C D E A B C D E A B C D E A B C D E A B C D E A B C D E           TABLE2         COL1 COL2 COL3 COL4 COL5 A B C D E A B C D E A B C D E A B C D E A B C D E A B C D E A B C D E   PROC IMPORT DATAFILE="/PATH/test.xls" OUT = UPSTREAM DBMS=XLS REPLACE; SHEET="Sheet1"; GETNAMES=YES; DATAROW=2; RANGE="Sheet1$A1:E9"; RUN; PROC IMPORT DATAFILE="/PATH/test.xls" OUT = DOWNSTREAM DBMS=XLS REPLACE; SHEET="Sheet1"; GETNAMES=YES; DATAROW=2; RANGE="Sheet1$A11:E19"; RUN; Hope this helps     ... View more

Hi mate,   I have some questions. This only happens when you re open the SAS EG ? If you re-define these macro abbreviations will it work in this session ?       ... View more

If you have the error message, or warning could you show us ? SAS Enterprise Guide 6.1   Tks ... View more

Hi friend,   I think this might help you.   There and back again: copying files in SAS Enterprise Guide   SAS® Enterprise Guide® 5.1 and 6.1 : A Powerful Environment for Programmers   Hope this helps     ... View more

@cstopp, check out... By @ChrisHemedinger   SAS manages the memory for you, so it's similar to Java or .NET in that way. But there isn't a garbage collection mechanism per se. SAS programs consist of a series of "steps" -- the DATA step and PROC steps (for SAS procedures). For the most part, memory is allocated as needed during the running step, then released when the step is complete.   Some SAS procedures can use a lot of memory during the course of their work, and you can run out of memory when working with large data or data sets with large cardinality. For example, PROC FREQ can compute n-way frequencies quickly, but if the variables you're analyzing have lots of distinct values, you can bump into memory limits. When this happens, SAS will issue an ERROR message to the SAS log indicating that there wasn't enough memory to complete the operation.   The SAS DATA step also offers some constructs that are inherently memory-dependent. The most popular is thehash object, which allows you to load lots of data values into memory and manipulate them quickly. It's good for building fast data management algorithms, as long as the data values can fit into memory.   Finally, when we talk about memory management in SAS, we also have to address the WORK area: the temporary scratch space on disk where SAS can write files as intermediate results while SAS procedures run. In practice, most SAS programs that deal with large data sets will run into WORK space limitation before they hit memory constraints. On administered SAS environments, it's important to ensure that SAS programs have access to enough WORK space (ideally with fast I/O performance) to accomplish their work.   For more admin-friendly tips, see this series of blog posts from my colleague Margaret Crevar.   Check out this How does memory management work in SAS?   ... View more

Hi mate Maybe try to use:   options compress=yes reuse=yes; Maybe this can compress a little your results. Or try MEMSIZE System Option: Windows   Hope this helps ... View more