Furthermore, The python-generated Excel file has the headers.   ... View more

The python-generated Excel file has no header warning.   If I test an Excel file with headers created using Excel (not created using SAS or Python), I don't get the header warning from the inspector. ... View more

Apologies for posting the reply here after replying via email. But, the Python-generated Excel file has no  “! Headers and Footers” warning from the Inspector.   ... View more

But, the Python-generated Excel file has no "! Headers and Fotters" warning from the Inspector. ... View more

I do want the header, not the warning from the running of the Inspector in Excel. ... View more

Your comment (false positive) regarding the warning about the absolute path for the SAS-generated Excel file is interesting.  I got the same warning the for the Python-generated Excel file from the analysis of the same data  when checking it in Excel.   However, the real issue is that I got the "! Header and Footers" warning only for the SAS-generated Excel file, not for the Python-generated Excel file.  This issue seems to cause an warning message when comparing the two Excel files using a Python Program.    The question is, What changes do I make to the SAS code submitted to avoid the warning from the  Excel "File->Info->Inspect Workbook->Inspect Document->Inspect"?       ... View more

1) I agree with you  about  the use of  EXPANDTABS on the INFILE statement, which I have added to the code below. Thanks for clarification! 2) I want only one "year" value per observation from each record. That is why I did not use the @@ at the end of the INPUT statement in the code below. 3)  I have used the  TRUNCOVER option to eliminate the  note, "SAS went to a new line" message. DM "Log; clear; output; clear; odsresults; clear"; filename source temp; proc http url = "https://meps.ahrq.gov/data_stats/download_data_files.jsp" out=source; run; options generic; data year_values; length year 8; infile source dlm='<' expandtabs truncover; input @'<option value="' @'>' year ??; if not missing (year); run; proc print data=year_values; run;     ... View more

Sorry, I  would like to add the following comments, which I missed earlier.   1)  It seems that the EXPANDTABS option on the INFILE statement is redundant. To avoid the following note in the SAS Log, I used the TRUNCOVER option on the same statement. NOTE: SAS went to a new line when INPUT @'CHARACTER_STRING' scanned past the end of a line. 2) To get the desired results your earlier code  works fine.  infile source dlm='<' truncover; input @'<option value="' @'>' year ??;   filename source 'c:\Data\web_data'; proc http url = "https://meps.ahrq.gov/data_stats/download_data_files.jsp" out=source; run; options generic; data year_values; length year 8; infile source dlm='<' truncover; input @'<option value="' @'>' year ??; if not missing (year); /* no invalid year values possible */ run; ... View more

  Here is the revised code I tried. It has worked for me.   Question 1:  I did not use the @@  in the INPUT statement because the data file does not have multiple  YEAR records on the same line. Does not using the @@ make sense to you? Question 2: Sorry I could not find the @Syntax of INPUT in the SAS(R) Documentation. Could you please send me a reference, if possible? Question 3:  What does the generic option on the OPTIONS statement do? Any reference? Thanks,     options generic; data year_values; length year 8; infile source dlm='"' expandtabs; input @'<option value="' year ??; if year in (1900:2023); run; proc print data=year_values; run; ... View more

Correction" input @'<option value="' @'>' year ?? @@; ... View more

Sorry, I got  three more  clarification questions.   1) In DATA step below, I have changed the conditional IF statement to 'if not missing (year);'  in order to filter out  the observations with missing values for the numeric variable year.  Does this code change make sense to you?   2) The  @'<option value="' will cause SAS to move  its  pointer past the '<option value="' field.  Then  the  @'>' will make SAS move  its pointer past the '>' field to read the numeric value, for example, 2021 (not "2021").  Is this a correct code explanation?   3)  The ?? modifier suppresses  the following  notes (examples from the partial SAS Log), NOTE: Invalid data for year in line 738 39-57. RULE: ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0 738 <option value="All">All available years</option> 66 year=. _ERROR_=1 _N_=1 Is this a correct code explanation?   Thanks,   options generic; data year_values3; length year 8; infile source dlm='<' expandtabs; input @@'<option value="' @'>' year ?? @@; if not missing (year); list; run ... View more

Hi Tom, Thank you so much for sending me two solutions to reading highly unstructured data into SAS.   Questions: Why does SAS issue the following note? Is this something that we need to be concerned about?   NOTE: SAS went to a new line when INPUT @'CHARACTER_STRING' scanned past the end of a line   ... View more

format html_line $char50.; Adding the above SAS statement did not change the output. ... View more

Hello Tom, Mine is from the listing output, not the ODS output. Do you see anything wrong with the NPUT statement below? I used a similar syntax for hundreds of PROC HTTP response data files. No issues, Thanks, data year_values; length year $4; infile source length = reclen lrecl = 32767 end=eof; re = prxparse('/(\d{4})<\/option>/'); /* Read the HTML line by line */ do while (not eof); input html_line $varying32767. reclen; Len_html_line = length(html_line); /* Match and extract the years using regular expressions */ if prxmatch(re, html_line) > 0 then do; call prxposn(re, 1, start, end); year = substr(html_line, start, end); output year_values; end; end; run; ... View more