A lot of customers don't use Viya and have no plans to do so. If Viya is part of their path, agreed, but it may not be.  ... View more

[Edited to removed ODBC-AC] SAS datasets can be read 100% using ODBC/OleDb without a SAS server using the drivers from SAS. There are 3 providers. Use local provider not IOM or Share. Use it all of the time at client sites. ... View more

Patrick is correct. SCL/AF is last century. It is a way to bring up a Window display in the old SAS DMS editor. It is old, old school SAS. EG is a C#/.NET application. You can create dialogues in it using custom EG tasks. They are simply C# code implementing a few interfaces. Chris Hemendinger has numerous examples. However, I suggest just pulling the parameters out of a window and putting them into some macro vars at the top of the code. Not worth building a UI part unless it is very complex. ... View more

One thing to keep in mind, SAS/Access to ODBC is a push operation from SAS and requires SAS to run. You can also use a pull operation using the SAS ODBC driver, which is free, and pull the data direct into PowerBI. ... View more

Suggest using ODBC vs OleDB. You install the package on the machine with PowerBI. Use a SAS connection string for the driver (see SAS connection strings - ConnectionStrings.com). It depends on your SAS installation and needs. I use the local provider since it allows for direct connection to SAS datasets. Your needs may vary.   OleDB is newer but was a MS standard that was never fully embraced. the industry stayed with ODBC despite its age. JDBC is good but has issues with .NET (hence, a good chunk of the MS ecosystem). ODBC is the safest bet but OleDB may work for you.  ... View more

I am out on a limb here since it has been years since I worked with SPDE. The sas7bdat is a binary proprietary format. SPDE files should be in that same vein. However, the sas7bdat and spde are both ODBC compliant. Download the ODBC drivers and use them vs using the binary readers.   For simple SAS data reading, use ODBC and OleDB where possible. They are not perfect but they should give you what you need. This also keeps you from needing R to read a SAS binary protocol. ... View more

I am speculating here so bear with me. The EG guys can correct if I miss something.   EG is a .NET/C# app (I am a SAS and C# dev so I kind of know how this works). When you make changes to an EG project, it saves them to the in-memory object (classes). When you save, it has to serialize them to XML. When you open a project, it deserializes them back to the objects. Any time you are serializing a large object, it can go wrong. Shouldn't, but it can. depending on what happens in the I/O. Especially true over a network connection. I suspect something blipped in the serialization.    You really need to make the project smaller. I have never seen an EG project of that size and I look at them a lot, especially in their raw form. I rarely use EG as an application, mainly deal with the EG zip file or making EG add-ins. If you have data stored in the project (which I suspect), move it elsewhere.   ... View more

Ignore the warning or, make a copy of it and do the rename. The warning is a standard Windows thing. ... View more

Thanks Allan, very good to know. I wasn't aware of the WASM issue. ... View more

Raw javascript is, well, less than palatable IMO. I would suggest a framework that hides JS a lot (ex. ASP.NET, React, Vue) if web is goal. I personally use Blazor (web assembly) but that is a bit much if starting out. If you dont need a web interface, you can use WPF or WinForms. If you need cross-platform, look at WinUI. If you want it simple, look at PowerApps. You can call Allan's library using any of the above. Not an either/or situation. ... View more

Not every aspect of non-code EG can be automated via code. Normally, you automate tasks using C# and the EG .NET libraries. However, this seems like overkill here. You can automate every aspect of EG using an RPA technology. For example, Power Automate is built into Windows (free) and can replicate everything you do in EG.   Simplest solution: write a SAS program, as Quentin mentioned, and automate that. If you want a new super skill, look at RPA.   ... View more

Use the X command, call Powershell, and run the SSIS package using Powershell. Your environment may not allow the X command so get back if it doesnt. See this documentation from MS: https://docs.microsoft.com/en-us/sql/integration-services/ssis-quickstart-run-powershell?view=sql-server-ver15 ... View more

SAS server is not required to read a SAS dataset. Only the SAS ODBC driver. ... View more