I never suggested refactoring your whole code base. If you have code that works, stick with it.   As a Microsoft/SAS consultant, I am just telling you what I encounter in the field. A company has nowhere near the variation as what I see across dozens of companies so YMMV. In this case, switching it to a DBMS source may eliminate the object type issue. As Quentin said, "N/A" breaks a numeric column. It does in SAS, under some access methods, but I can get around it using different tech. SAS does not have a concept of a try/catch block and SAS is a loosely typed language. Excel cells are an object, not a value. SAS has to treat it as a value but a cell is a container with properties, methods, etc. Same with rows and columns.    Excel is best read with Excel or Office type products. Whether it is Office interop or 3rd party libraries such as GemBox or Aspose, there are much faster, better ways to read Excel. SAS works and I have used it a lot. However, if you have to create 10K worksheets a day, SAS cannot do it (yes, that is a real volume from a real SAS client). Interop can't do it effectively either. If you have to read colors or bold/italic, it is hard w/o the metadata access.   If it is a SAS bug (looks like it) then they can fix it. In the meantime you work around it or wait for a patch. I would choose the former but your call.              ... View more

SAS has never worked with Excel very well. Excel may be the largest storage format, for numbers, in the world. I do not use SAS with Excel directly but use other tech to work with Excel and feed it to SAS. I love Excel as do millions of others.   As a Microsoft/SAS consultant, almost every engagement has involved Excel. If you are encountering issues with SAS, and want to solve it in SAS, I suggest using the libname (as Quentin stated), or OleDB to read data.   Excel is not a good datasource but people love it and it is a standard. Excel was not created to be what it has become but so what? Can SAS read the cell color, italics, spacing, and other weird ways people layer metadata onto values? I dont think so (correct me if I am wrong). Hence, I usually go around the SAS/Excel dilemma and have each do what they are best at. I use intermediate tech to handle the data back and forth.   If you don't face these kind of dilemmas, use Quentin's suggestion or a db tech. ... View more

Well, you could also consider doing it w/o using PROC IMPORT. ODBC, OleDB are both viable as well.   If the formats, formulas, styles, etc. don't matter, treat Excel as a data source.     ... View more

Tom suggested, in an earlier post, to release the filename. I didn't see that after cursory review. Have you tried it?   filename myFile 'blah, blah' ; proc import...; filename myFile; <== Do you have this in place? ... View more

You can also schedule using PowerShell.   Scripts can be seen here: https://stackoverflow.com/questions/42801733/creating-a-scheduled-task-which-uses-a-specific-event-log-entry-as-a-trigger   If you don't have security, PowerShell should tell you directly.    ... View more

Try this (with your changes):   libname SQLREF ODBC NOPROMPT="server=SVDSQLDCP01;driver=ODBC Driver 13 for SQL Server;trusted_connection=yes;database=DEVAPP10_Shredding" STRINGDATES=NO IGNORE_READ_ONLY_COLUMNS=YES SCHEMA=DBO;    From here: GitHub - savian-net/SasTipsTricks: Tips and tricks learned over 20+ years as a SAS/Microsoft consultant   ... View more

C#, not C++.   Custom tasks live on your side of the equation. You load them via the EG menu.   Chris' examples make it easy to customize. You can copy his code and modify as needed. You have to comply with the contract (i.e. interface). Ex. Martin  object implements IHuman and IMammal and therefore has certain properties and actions.    Your call but a way to fix the issue. Just wanted you to be aware of it. You could do a follow along on a simple task and see what you think.  ... View more

Consider creating a SAS Custom Task. I haven't done this in a while so bear with me.   SAS EG is written in C#. You can make a custom task that takes parameters (custom UI) and loops the tasks. I have built these for SAS clients before who were in a similar position. There is a C# interface you have to implement and then code up whatever you want. You are limited to the Framework but that is more than enough power.   See this page and book on how to do it or refer to examples online. I have C#/SAS examples on my github site as well. There is also a program there that extracts out the SAS code from EG. However, I think a custom task works better (or is at least worth looking into). ... View more

Prelim version that does a bare minimum, for now. I left out the parsing and reporting for SAS code so you can accomplish the bare minimum (extract code):   savian-net/SaviEg: Extracts SAS EG projects into SAS code and does reporting on contents (github.com)   I will add in the other bits over time. They are coded but in a different project. Let me know how it goes.   I also made it x64. .NET 5+ runs on all major platforms so the code could run as portable but I don't have another OS (outside of Windows) installed. If a need arises to support Linux, I can recompile and someone can test it.  ... View more

Will do once ready. I started work last night on making it accessible from the command line.   I will update this thread once ready (next week, hopefully).  ... View more

I have the code to do this. Will try and get it to github as a console app.   It will use .NET 8 if you are interested.    ... View more

Agreed Jim, IML is not free.  ... View more

Since you are new to both, I suggest never using vbs. It is way out of date and will cause security issues. It is slated to be removed by MS and has been deprecated a long time ago: VBScript - Wikipedia   That said, what are you trying to do? There are other ways to handle what vbs did. ... View more

Rename the EGP to a zip extension (ex. MyProject.egp ==> MyProject.zip). Examine the files. They are XML files and one of them will contain the SAS code.   ... View more

The source code is there. You need to run it from source and see where it throws. Look at the binary file and see if you have something such as COMPRESSED in the hex codes. It is impossible for me to guess at what may be causing it since I don't have the data. Open up the file in a good hex editor (UltraEdit, NPP, or 010 Editor which is what I use) and see what is happening. The code will guide you through it. Just step the code.   SAS also changed the xpt layout and I couldn't figure out the new layout (their documentation was off in one area). I don't think you have that but you need to look at the hex and see where things are off.    I looked at the code and the error you are showing doesn't tell me where the error is located (line #) or anything meaningful. There is no way you are blowing up on the value of an int and Observations is a List. Not much I can do to help w/o info and that requires stepping the code to see where it fails.   ... View more