That should be fine. It is very simple to use a DB as well. You need SAS/Access to ODBC/OleDB/etc. but a db is optimal here. ... View more

I use Git a lot. then again, I am a C#/SAS coder and C# uses Git all of the time. I know Git is integrated now into EG, which I have not used yet, but I can tell you how it works in my C# world. Same holds true in SAS world. Read papers by Chris Hemendinger on git in SAS. They should be great. Here is one: https://blogs.sas.com/content/sasdummy/2019/01/17/git-in-sas/ Git operates with a local repository which stores your changes. When you make changes, they are committed locally. Once you are comfortable with all of the local changes (commits), you need to push the changes to GitHub. 2 step process: commit then push. I am not aware of any SAS community that helps with SAS/Git integration. HTH ... View more

A SAS dataset is not designed to be used in a shared configuration like this. It is a simple, physical file on a disk. Reading is probably fine but writing is bad. You are probably seeing file locks happening.   Find a storage mechanism that handles concurrent access such as a DBMSs (ex. SQL Server). ... View more

This somewhat looks like an Excel file saved as XML. Try something simple to start. Change the file extension to xlsx and see if Excel opens it. I doubt it but worth a shot.   [UPDATE: You need to make sure you zip the file first then change the extension]   Excel xlsx format is merely a zip containing XML files. This looks like the main body file of an Excel file.   Also, don't get too worried about XML. It is merely 2 parts: elements and attributes. Elements are like:   <LastName>Smith</LastName>   Attributes occur within the element:   <LastName type="string">   There are no secrets with XML. It is 100% dependent on the engine that reads them. The developer determines what elements and attributes to use. If you want to have an application handle it for you, and convert it to something else, look at the online XML engines like: XML To CSV Converter (convertcsv.com). There are lots out there (search XML to CSV, for example). The XML you have is Excel XML. Try and use its engine to start and don't try and parse it yourself.    ... View more

Martin,,   Parse the EG xml. Get the SAS programs. Create a loop to execute each one using a code prepend of the following:   options mfile mprint obs=0 noerrorbyabend errors=0 source source2 nonotes; filename mprint 'c:\temp\[INSERT_NAME].txt’;   Then, parse the [INSERT_NAME].txt file for the datasets.   Parsing SAS code is not trivial (aka years of work). The above gives you a means of resolving the macro code: that is more than half the battle.    Here is an example piece of code to illustrate:   options mfile mprint obs=0 noerrorbyabend errors=0 source source2 nonotes; filename mprint 'c:\temp\TEST_SAS_MPRINT.txt';   data _null_; file mprint; run;   %macro getData(ds=);    data test;       set &ds.;    run; %mend;   %getData(ds=sashelp.class);   options mprint;   ... View more

GDI+ are your graphics drivers. I would make sure your graphics/printer/pdf drivers are up-to-date. Run Windows Update as well.   Start there then call tech support. ... View more

SAS egp files are actually zips of XML data. Read in the egp using a zip library, replace the instances in the XML of the old path, zip, save back as egp files. Test it on a few programs.   This stuff is best done in another language. I prefer C# but use whatever you want (python, for example). For an experienced developer this is ~1 hour of work.    You could treat the XML as a string and use a regex to do the replace or use an XML engine.   So, in order:   1. Read egp files with a zip library 2. Change XML nodes where path needs replacement. OR, read in whole file as a string and replace the path using regex/string replace function 3. Save file back as an egp using a zip library   HTH, Alan   ... View more

Between MS butchering their HTML links in current releases and SAS stripping it out, the links are wrong (mainly blame MS).   Look here:   Creating a workspace session using SAS IOM & VBA - Stack Overflow   WUSS02.tif (lexjansen.com)   You just have to search properly. Look for SASWorkspaceManager and VBA. Toss in IOM if you need to. ... View more

Well, he has but his name is probably not on it. It was a long time ago. Look at LexJansen's site which has the SUGI/SGF archives. For example, WUSS02.tif (lexjansen.com) <> The technique you need is old but the papers are out there. Find some keywords and go searching. For example, VBA/SAS Cookbook/LanguageService/SASWorkspaceManager I have some code I am happy to share on IOM but it is in C#. You need to translate that to VBA. You are swimming uphill, however, since what you need to do can be done outside of VBA and there are code examples. The choice is simple: learn some basic C# or try and find nuggets of VBA code. You could also ignore the direct integration and submit SAS at the command line on the system where SAS is installed and capture data using stdout. ... View more

He wrote a lot (I believe) where his name is not attributed. You need to try and convert the .NET to VBA. There is no easy way. You can check here for a possible scenario: VB6 Migration Tool for .NET <>ize.net%2Fproducts%2Fapp-migrations%2Fvbuc&data=04%7C01%7Ccommunity.admin%40 sas.com%7C7060699a9c084c43e2d908d8cc7756b0%7Cb1c14d5c362545b3a4309552373a0c2 f%7C0%7C0%7C637484160959504973%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=Ts2xmJDcbnOkjOppp 3aH6oQeg3b5AJiAEqtv3mxvMC8%3D&reserved=0> & C# Converter - VBUC | Mobilize.Net ..or, 1) switch to C#. I would choose the latter. VB6/VBA have nothing in common with .NET. You can call the dlls but almost all examples for working with SAS are in C#, including mine. Thanks, Alan ... View more

Yeah, I don’t use Google for search. I am a Bing guy (SAS/Microsoft consultant) …plus, I hate Google 😉 ... View more

Well, he runs this site 😉 Here are some links: Chris Hemedinger, Author at SAS Blogs https://www.amazon.com/Chris-Hemedinger/e/B003579A9M?ref_=dbs_p_pbk_r00_abau_000000 Also look for the Integration Technologies Cookbooks. Here is an example (it is 9.3 but still valid): Connecting to a Remote SAS Workspace Server Using SAS Objects - 9.3 ... View more

This is SAS-related, not VB or VBA (different things. There is also VB.NET).    It has to do with the COM libraries used with SAS/Integration Technologies. When you are using SAS/EG, you are most likely connecting to a SAS server somewhere. Hence, you are not using a local version of SAS. SAS is executing elsewhere. SAS has 3 providers (Local, Share,  and IOM). You need to find examples using IOM, not local. You have to execute your SAS code on a remote instance and then get the data back.   Look for articles by Chris Hemendinger on IOM and VBA. You can also glean some knowledge from his articles on VBScript (another variant), PowerShell, C#, etc. Share may also work but IOM is probably your best bet.   EG does not have to use a SAS Server but based upon your comments, it probably does.   Any chance you can get a local instance of SAS? ... View more

Where is sas.exe being executed? ... View more