Excel for mac file in compatibility mode won't open

excel for mac file in compatibility mode won

#Excel for mac file in compatibility mode won't open how to#
#Excel for mac file in compatibility mode won't open code#

Suddenly found all Word documents opened read only. The only way she was able to get around the problem was to turn off the automatic backup file feature in Word (Tools | Options | Save tab, clear Always Create Backup Copy) while working in that document. It wouldn't happen to all the documents, but once it did happen to a particular document, it would keep happening to that document no matter what she did. We've not been able to discover the real cause for this problem, but one of our subscribers reported that she experienced the same problem with some Word 97 documents. Suddenly, the status of the file would change on its own, and when John tried to save again, Word wouldn't let him because the file was read-only. It doesn't do this right after opening the file, but at different times while using the document, and most of the time after the file had already been saved a couple of times. It seems that Word periodically, and without warning, converts a file to 'read only' while it is being used. If i_item.Priority > j_item.Subscriber John McQuillan ran into a problem with one of his document files. Set theMatches = cellvalue_regex.Execute(fc.Formula1)ДЄДim i_item As FormatCondition, j_item As FormatCondition Sub FlattenFormats()ДЇor Each c In (xlCellTypeAllFormatConditions) This leaves the workbook formatted but removes the cause of the compatibility checker being forced to appear. In a nutshell, this goes through all active cells, and for any cell containing a conditional format, evaluates whether or not the custom formatting should be applied (in the correct order), then manually applies it. Note that this doesn't address the compatibility checker in all cases, just in case of overlapping custom formats. I need to be able to turn off compatibility checking at run-time for any workbook, the first time, without human intervention.Д¬reated a workaround that isn't completely full-featured but it at least hits everything I personally need maybe it'll serve as a launching point for someone else. I mean, I suppose I could, but that would become my full-time job. Because this happens on dozens of different template workbooks every two hours on an unattended system, I can't simply uncheck the compatibility requirement on a per-workbook basis. xls file (per the vendor's requirements).

#Excel for mac file in compatibility mode won't open how to#

Anyone have any idea how to suppress the checker even with 'significant' incompatibility?Д®TA: Without going into a lot of unnecessary detail, I'm trying to automate a process where a number of vendor templates are opened, populated with data, processed according to an enormous (and always slightly different) set of quality control rules, and saved back out as an. (v=office.14).aspx) but nothing I do seems to suppress this error, not even creating a registry entry to disable it. I suspect this is because the error isn't a 'minor compatibility issue' (cf. The compatibility checker still comes up.

#Excel for mac file in compatibility mode won't open code#

Once the code has completed, choose the Excel 97-2003 file type and click 'Save.'.

If you step through the code, you can verify the CheckCompatibility setting in the Immediate pane. The code will immediately jump to the breakpoint.

Back in the spreadsheet, select File > Save As.

Open the VBA editor, and add the following code to the Workbook module: Private Sub Workbook_BeforeSave(ByVal SaveAsUI As Boolean, Cancel As Boolean)ДЄctiveWorkbook.CheckCompatibility = False A2 should have two different conditional formats applied.

Select A2:A3 and choose a different conditional formatting.

Select A1:A2 and choose a conditional formatting (doesn't matter what).I've found that, while it's possible to programatically disable Excel's 'Compatibility Checker' via code (by using ActiveWorkbook.CheckCompatibility = False, either before a SaveAs call or globally by trapping the ActiveWorkbook.BeforeSave event), it doesn't seem to work if there is a 'Significant loss of functionality' detected.