If I understand correctly, what you would need is a SQL parser. From there, you could use the syntax tree to generate the Query Builder components and/or movements if simulating a UI.   SQL parsing is not a trivial task. Combine that with the fact that SAS SQL is a different syntax than just ANSI SQL and you have a real challenge.    Ultimately, it will be far more work for you to do the parsing. You can look at generic parsers for SQL but they tend to be specific. After getting the statements parsed out, you then need to automate the query building process.  Better SQL parsers are very, very expensive.    If you have repetitive tasks that can be logically described in a UI, use UiPath and script the human movement. UiPath is an RPA tool and can dramatically speed up repetitive manual tasks. You should be able to use their desktop version. Takes a bit of getting used to but you will never go back to manual, repetitive tasks again. Wonderful product. ... View more

I have made numerous custom tasks in C# for EG. It isn't too bad. They can be used by other EG users and appear in the available tasks. They can be full-blown applications with numerous Windows, etc.    EG has a few interfaces that have to be used. Visual Studio auto-implements them and you fill in what needs to be done. If you haven't worked with interfaces, see this  to understand them a bit. It will help when you read Chris' book:   (1) Interfaces in C# - What they are, how to use them, and why they are so powerful. - YouTube   Basically, they are a contract. It allows EG to call your custom task. For example, a car may have a IVehicle interface. All vehicles must explain how to accelerate. In EG, you will have contracts like 'RunTask' that tells EG what to run when the task opens.      ... View more