libxlsxwriter VS Node-Excel-Export

Using libxlsxwriter and libgit, it's straightforward -- just putting the equivalent of git shortlog and lines added and removed into a line of cells.

We'd negotiate to add spreadsheet export only, no import, and then use a library like libxlsxwriter to export a read-only sheet, or configure a read-only ODBC connection to the database.

Linking spreadsheets to a SQL database is done with a database-specific ODBC driver. When we've migrated spreadmarts in the past, I've written simple .xlsx file code using libxlsxwriter to generate read-only and read-write spreadsheets.

If I was in your position, I'd get A, B, C, and D to send TSV (or DIF, SYLK) -- UTF-8, no BOM! -- to you, then I'd write code to put it into a conformant XLSX file, then submit that. That puts you in a good business position by tightly controlling what gets sent. I hope you weren't trying to keep metadata from A, B, C, and D from going to Z, who might choose to solicit them directly for a business relationship.

We started phase-down of general-purpose filesharing a long time ago. Many of the migration strategies involve making it read-only. In some cases I replaced a shared spreadsheet with an automatically generated one. Read-only spreadsheets that link to a real database over ODBC are an old favorite. I'm happy to give legacy views into database-backed webapps where we can.

Based on some of the weirdness in the XML, it looks like Vendor A might be using Node-Excel-Export to do their conversion and my problem isn't the only instance I can find of half-working XLSX files resulting from it.