Also if your SAS Compute server runs on Windows, then you can remote into it and create a test data source in the ODBC Administrator then use the Test Connection button. That way you are taking SAS out of the loop and can demonstrate that failures are purely a data connection problem.  ... View more

Please do not separate error messages for the log of the code. Typically SAS provides diagnostic characters placed in the code for some of these messages and it is much easier to diagnosis with the entire log of the procedure. Copy all of the text for a procedure with all of the notes, not just errors. Then on the forum open a text box using the </> icon that appears above the main message box and paste all the text.   Likely the No matching DO is coming from here: compute babydate_character ; count + 1 ; if mod( count, 2 ) then call define( _row_, 'style', 'style=[background = cxd9d9d9]' ) ; else call define( _row_, 'style', 'style=[background = cxe9f3ff]' ) ; end; ENDCOMP; There is nothing indicating a DO or Select prior to that end in the compute block. Likely the cause of the "Statement is not valid" as well. ... View more

It worked.   I had to apply it to the dataset, not the proc report.   data bororeport_Rearranged3; set bororeport_Rearranged3; babydate_character=put(babydate,$monyy7.); run; ... View more

Thank you! I defined the length of AFORF1, and it worked.  ... View more

You usually mark the solution that is the answer, especially if there are multiple answers,. ... View more