> What it really needs is full blown SQL with REPL output so the users can see the effects of their SQL. FWIW, I built a version of this at $DAYJOB. You can ge

> What it really needs is full blown SQL with REPL output so the users can see the effects of their SQL. FWIW, I built a version of this at $DAYJOB. You can get REPL-like access and export to Excel using a tool like this: https://azure.microsoft.com/en-us/products/data-studio https://azure.microsoft.com/en-us/products/data-studio Non-software engineers looked me like I had ten heads for suggesting that people would need to learn a modicum T-SQL to make use of it. I even volunteered to write all the views for them! The lesson learned for me is that horrible expensive ERPs/ETLs tools are never going to be replaced with Excel + a database because even the (non-software) engineers at a large company are not interested to learn how to write basic SQL statements.