This works fine in interactive mode, but doesn't if you use Windows Task Scheduler to run the SAS program that uses this script to convert xls files to xlsx files.  The vbscript does not even launch.   Do we have something that works for a scheduled reporting program? ... View more

Great help, It makes me understand the concepts better now. ... View more

Thanks, it seems like there are a couple ways to go about it.  I have learned a lot about how input works from reading these responses.  I made 3 changes to my original code to get it to work perfectly.  2 were to add DSD and TRUNCOVER options (did not have these before).  From what I gather the DSD is what makes it recognize my delimiter.  The 3rd was to add the colons before the informats input CLCODE : $1. AGENT : $5.; From what I gather, in effect, this makes SAS do the same sort of check your code is performing.  It only pays attention to the informat so long as it has not hit the delimiter.  So if there is a blank, once it hits the delimiter it moves on, rather than inputting the delimiter. I think your example would be a way to get it to work too though. Thanks again to all for the help. ... View more

And since this is a result of the "File Save As" in Excel it isn't possible directly with ODS. A work around using DDE is possible but is fragile as Excel version, file types and command syntax changes. It was worth it to me as I had hundreds of files to do the "File Save As" to. See https://communities.sas.com/thread/34669 ... View more

I like to use %if &city ne %str() %then %do; instead of leaving a blank space...just because it is more obvious to me ... View more