I have been using 360Works Scribe for a client for a critical workflow of theirs. M$ dropped an update last week on Office and now Scribe can't read an Excel file. Files created with Excel versions up to and including 16.10 are read fine, but anything created with 16.11 (the version released this past week) import what looks like unrecognizable binary data. Aaaaaaannnnnd, wouldn't you know it, every person in their company upgraded like good little computer users.
While I really would love to give the good folks at 360Works all the time they need to fix this, my client is, shall we say, impatient.
Does anyone else have an idea to remedy this sooner rather than later?