[813919]

This is incredible. I work in industrial automation and I often have to manage / make edits to "point assignment charts" which are essentially Excel Workbooks with 100+ Worksheets, each containing ~10-100 rows of formatted data which define various parameters each real world "point" should have in order to communicate with RTUs / various SCADA nodes.

Sometimes the feedback involves making a minor tweak on every Worksheet. Sure you can muck around with VBA (which is a horrible language and experience), but I often just do it manually to get it over with instead (click click click... very tedious).

C# is my go-to "business logic" language as a developer, and this looks so well integrated, really excited to use it.

[jodrellblank]

> "Sometimes the feedback involves making a minor tweak on every Worksheet."

Could be a good task for PowerShell and the ImportExcel module[1].

(PowerShell also being a .NET language and written in C#; it has convenient access to COM control of Excel if you can't import the spreadsheet and export an updated version; through $xl = New-Object -ComObject Excel.Application )

[1] https://github.com/dfinke/ImportExcel

[cm2187]

You should look at spreadsheetgear. Great .net library for spreadsheet manipulation, which also has its own calculation engine (though it doesn't support xlsb and pivot tables).

[anakic]

Would love to know how you get on with it. If you'd care to share, please to let me know.

[813919]

Sure! I'll make a reminder to follow up a week from now on my UX. Thanks :)

[kevin_thibedeau]

You have inherited a crappy database. Export it via ODBC and use more powerful tools.

[813919]

No not really, it's many projects with many documents, shared among many contractors. You use Excel Workbooks when you work in fields like this. We have it formatted to be pretty too, so we can just publish to PDF via Adobe Acrobat when it's time to send in submittals.