P.S. that known issue for David is only as a result for upgrading from 7
to 10 and the upgrade process slightly mangles the Office click to run.
As you state that's long since fixed and is not your fact pattern.
I know stating the obvious....
On 4/18/2016 10:46 AM, Susan Bradley wrote:
I think that still would be the best resolution. 2016 natively has
blocks to ensure that malicious files/macros don't run. Moving off of
XLS to XLSX ensures better interoperability.
On 4/18/2016 10:30 AM, Jim Majorowicz wrote:
sorry all for the late reply. I've got a similar problem for older
excel files created on a Mac not being able to being opened on an RDS
server with Office 2016. Did you have any luck fixing this? I'm
finding that they spreadsheet needs to re resaved as an XLSX in order
to be shared.
On Wed, Mar 30, 2016 at 7:10 AM, David L Herrick
<[email protected] <mailto:[email protected]>> wrote:
We have a vendor where our users can run reports and dump them
into excel. Machines with office 64bit all work fine.
32 bit get the corrupt message have to do a save as of the file
and it them opens fine.
Vendor says it is a known problem and following the link you can
fix it.
https://support.office.com/en-us/article/Errors-opening-Office-files-after-upgrading-from-Windows-7-to-Windows-10-4ceecee4-c4bb-47cd-9566-2b3a3997418e?ui=en-US&rs=en-US&ad=US
We are well above those requirements. Anyone heard of this?
Thanks
David
