Thanks Cynthia - I've not seen this type of behavior before with symbols.  I started a case with SAS TS. ... View more

B = Baseline    I originally chose to abbreviate the words then wrote them out. This has no impact on what the output is doing. ... View more

As long as I don't use unicode symbols and just type ">=" no extra space.   The font is default for PDF (Sans Serif perhaps)? ... View more

This I understand - what if I want to use a different dataset variable to set another attribute? I want to keep the colors as is that works; however, if I only want certain bars to have a crosshatch pattern based on another dataset variable, how do I do that? ... View more

This method does not work either. Bombs out on the same file each time.  ... View more

Ok - I see the following characters: Garbage line 1: VFMA_EyeSuite_ExportFormat=3.PatientID;<-this is the header on the next row Garbage line 2: VFMA_EyeSuite_ExportFormat=3.0000z;<---this also repeats on the third garbage line has a delimiter   When opening the file all I see is Format=3.    In the files that process correctly, this is what it looks like: Garbage Line 1: VFMA_EyeSuite_ExportFormat=3..Patient ID;<-double period Garbage Line 2: VFMA_EyeSuite_ExportFormat=3..0000z;<-same as the file that won't process ... View more

Log file: NOTE: The infile 'xxx.csv' is: Filename=A_zzz.csv, RECFM=V,LRECL=32767,File Size (bytes)=8530, Last Modified=31Aug2023:09:08:57, Create Time=31Aug2023:09:08:45 NOTE: 1 record was read from the infile 'A_zzz.csv'. The minimum record length was 3998. The maximum record length was 3998. NOTE: The data set WORK.OCTOEXP08 has 0 observations and 1158 variables. NOTE: DATA statement used (Total process time): real time 0.03 seconds cpu time 0.03 seconds 0 rows created in WORK.OCTOEXP08 from A_zzz.csv. The SAS System NOTE: WORK.OCTOEXP08 data set was successfully created. NOTE: The data set WORK.OCTOEXP08 has 0 observations and 1158 variables. NOTE: PROCEDURE IMPORT used (Total process time): real time 0.19 seconds cpu time 0.17 seconds NOTE: PROCEDURE SQL used (Total process time): real time 0.00 seconds cpu time 0.00 seconds WARNING: dataset A_zzz.csv did not import correctly This is the suspect file - all have the same layout. The data rows are the ones blacked out.  When I go to the end of the first line and manually hit delete several times, this takes care of the issue. Not sure what characters are causing it because they are non-printable.     ... View more

This didn't appear to work either. Still have files not importing because of extra characters of some kind that SAS is misinterpreting.   The code runs fine, but there are still non-printable characters causing issues somewhere. ... View more

I have a macro setup to read all the files, so that's not an issue. I need to remove the hard carriage returns from each CSV then replace the file before importing to SAS.   This seems to work - testing it now. It does seem to run a bit slow but with 300+ files to process I suppose that's expected. ... View more