Cursor behaviors are generally operating system or driver options. Information needed to even come close to helping would be your operating system, Version of SAS, was this in Base SAS, EG or another SAS application, type and model of mouse and possibly the mouse driver. The behavior sounds a bit like you may be pressing on the wheel of a scroll point mouse. ... View more

Hi RW9, Thanks for your help.....I was able to resolve the problem by modifying the Replic5 dataset fby adjusting the minimum and maximum unit prices first before the sub query. I t works perfectly. ... View more

Month should give you 11 estimates and Group 4 estimates. You should read up on how the class statement parameterizes categorical data. SAS/STAT(R) 9.22 User's Guide ... View more

From your SAS code piece, file WORK.TABLERANGES is sourced from a DATA step that inputs with a SET dates_info ab;  specified.  Neither of those two files has a SAS variable with the name you are getting for the SAS ERROR. ... View more

Hi Ballardw.....Thank you for your help. I ended up having to use  the statement " ods output ClusterHistory=ClusterHistory"  rather than select which created the dataset I wanted. Thanks once again. ... View more

Thanks everyone. Apparently, it looks like the INTCK Function does not like the LAG Function as part of the Start or End Date. I created another variable for the Lag claim date and then used the new variable with the INTCK Function and it seems to work fine now.....Thanks Once Again. ... View more

Well done, taking it this far.  Just in case there are still any issues, here a few comments. One of the PROC SORTs can come out: PROC SORT DATA=mydata; BY CID PRODUCT ID; RUN; The data had already been sorted, and they remain in order.  So the second PROC SORT isn't needed (check the log ... SAS probably figured out it should skip this second sort). If there is still an issue with the PRODUCT values, the suspect is here: PRODUCT = "&&PRODUCT&I"; That would be the correct syntax if you had already split &OBSERVATIONS into separate macro variables named &PRODUCT1, &PRODUCT2, ... &PRODUCTn.  Here, all you really need is the same syntax that worked in the %PUT statement: PRODUCT = "%SCAN(&OBSERVATIONS,&I)"; You may have already tackled that, so this is in the spirit of "just in case it helps". ... View more

HI,   It would be interesting to find out how you are using PROC REPORT to do an "export" to Excel. Are you using ODS? If so, which destination? Are you using PROC EXPORT? If so, which DBMS= option? Are you using the SAS Libname Engine for Excel?   If you are using PROC EXPORT or the LIBNAME engine, you may be able to use "named ranges" to export to a specific row and column position. Search on support.sas.com or in these forum postings for examples of exporting to a named range.    If you are using ODS, then the ODS destination output generally starts in A1. cynthia ... View more

Thanks to everyone who have made suggestions. I ended up creating another column (Group = ceil(_n_/100)) and used the Sheet_interval='bygroup' option to create a multi sheet excel file and it seem to work fine.....Thanks once gain to All. ... View more