I posted a zip file on page 1 of this thread.  ... View more

You are welcome to contact me directly and we can figure out approaches. alan.churchill@savian.net  ... View more

This works in Core 3.1.1 with nuget System.Data.OleDb and SAS Provider for OleDb 9.48. Solution attached:   static void Main(string[] args) { Console.WriteLine("Starting test..."); var dt = ReadSasDataset(@"z:\scratch", "shoes"); } private static DataTable ReadSasDataset(string sasLibrary, string dataset) { OleDbConnection sas = null; DataTable dt = new DataTable(dataset); try { sas = new OleDbConnection(@"Provider=SAS.LocalProvider.1; Data Source=" + sasLibrary); sas.Open(); OleDbCommand sasCommand = sas.CreateCommand(); sasCommand.CommandType = CommandType.TableDirect; sasCommand.CommandText = dataset; OleDbDataReader sasRead = sasCommand.ExecuteReader(); dt.Load(sasRead); sas.Close(); } catch (Exception ex) { sas.Close(); string errMessage = "Unable to get the SAS dataset. Library: " + sasLibrary + ", DataSet: " + dataset + ", " + ex.TargetSite.Name; } finally { sas.Close(); } return dt; }   ... View more

OleDb support in Core was a hot topic for a number of shops migrating from Framework to Core due to things like Access DB. It was added in in May 2019 and was put into Core 3.0 in Sept as a release.    I cannot say for sure that it will be faster. It requires testing. Heck, it may not work but give it a try in a small, isolated test project.   You are welcome to reach out to me directly as well. If I get a chance, I will try and test on my own.  ... View more

What are you using for .NET? Is it Framework or Core and what version,please. ... View more

I have a lot of C# around SAS. Here is a method to handle the read. I would defer to Chris H.'s suggestions and drop/keep as many variables as you can. Contact me directly for a dll if needed. The below is in Framework: I have not converted to Core as of yet. OleDb is in flux on core and I haven't looked at latest info.   public DataTable GetDataSet(string sasLibrary, string dataset) { OleDbConnection sas = null; DataTable dt = new DataTable(dataset); try { sas = new OleDbConnection(@"Provider=SAS.LocalProvider.1; Data Source=" + sasLibrary); sas.Open(); OleDbCommand sasCommand = sas.CreateCommand(); sasCommand.CommandType = CommandType.TableDirect; sasCommand.CommandText = dataset; OleDbDataReader sasRead = sasCommand.ExecuteReader(); dt.Load(sasRead); sas.Close(); } catch (Exception ex) { sas.Close(); string errMessage = "Unable to get the SAS dataset. Library: " + sasLibrary + ", DataSet: " + dataset + ", " + ex.TargetSite.Name; HandleError(MethodBase.GetCurrentMethod().Name, ex); } finally { sas.Close(); } return dt; }   public DataTable GetSasDataSetMetadata(string sasLibrary, string dataset) { OleDbConnection sas = null; try { sas = new OleDbConnection(@"Provider=sas.LocalProvider; Data Source=" + sasLibrary); sas.Open(); OleDbCommand sasCommand = sas.CreateCommand(); sasCommand.CommandType = CommandType.TableDirect; sasCommand.CommandText = dataset; DataTable dt = sas.GetSchema("Columns"); DataView dv = dt.DefaultView; dv.RowFilter = "TABLE_NAME = '" + dataset.ToUpper() + "'"; sas.Close(); return dv.ToTable(); } catch (Exception ex) { HandleError(MethodBase.GetCurrentMethod().Name, ex); return null; } } ... View more

Late to the party but that is ok.   I can probably figure out the VBA but rarely work with it anymore.   Suggestion for handling:   1. Get one of 2 products (both free)   - Visual Studio Code   - Visual Studio Express (Community Edition) - recommended 2. Install NuGet package EPPLus 3. Look at their examples in C# and lift samples 4. Execute   Yes, I know the above may be out of a comfort zone but it is far, far, far better than VBA. You don't even need Excel installed on the machine. It would take you a little bit to understand it, at first, but then you would blaze with Excel.  Plus, it comes with Intellisense so you don't have to hunt and peck for parameters.   If it something you want to consider, I can help you get something simple started. Just ping me.Would take 15 mins. There are also loads of tutorials and videos out there. ... View more

FlushList does work but you have to specify how many lines you want. See my simple example. ... View more

Just like there is a FlushLog,there is also a FlushList:   Here is a simple example of both:   static void Main(string[] args) { var ws = new SAS.Workspace(); var lang = ws.LanguageService; lang.LineSeparator = "\r\n"; lang.Submit(sasCode); PrintResults(ws, lang); } private static void PrintResults(SAS.Workspace ws, SAS.LanguageService lang) { SetColor(ConsoleColor.Yellow); Console.WriteLine("=========== LOG ============="); Console.WriteLine(lang.FlushLog(5000)); SetColor(ConsoleColor.Cyan); Console.WriteLine("=========== LIST ============="); Console.WriteLine(lang.FlushList(5000).Replace("\f", "")); ws.Close(); Console.WriteLine("Press any key to continue..."); Console.ReadLine(); }   I haven't run this code in awhile. Let me know if this works for you. ... View more

In C# (I don't do Java):   /********************************************************************* * IMPORTANT: The folowing 2 lines MUST be included even though they * appear to be unused *********************************************************************/ const LanguageServiceCarriageControl cc = new LanguageServiceCarriageControl(); const LanguageServiceLineType lt = new LanguageServiceLineType();   lang.FlushLogLines(1000, out Array carriage, out Array lineTypes, out Array lines); var lineList = lines.OfType<string>().ToList(); var typeList = lineTypes.OfType<SAS.LanguageServiceLineType>().ToList(); ... View more