When the June 28th patch is applied to existing Office installations XLS files generated by the Infragistics.Excel object are flagged as having a bad format and a "Do you want to continue?" dialog appears, if you say yes the file is opened successfully. XLSX files appear to be okay...
I'm currently using version 10.2.20102.2064, is there a later version that resolves this problem?
I don't believe something like this has been reported or fixed recently. I have forwarded this post to the Developer Support Manager and a DS engineer will be contacting you about this issue.
Thanks Mike. I inadvertently left out the name of the update which causes the problem: “Microsoft Office File Validation Add-in”.
(It evidently also causes extreme slow-downs in opening workbooks on network shares as well…)
Hello ,
The latest service release of 10.2 is 2151, so you could download it and test your scenario.
Also I have tried to reproduce your issue on my side with mentioned release, but I was not able to get the behavior that you described. I am sending you the sample that I have created. Please run the attached sample and press “Export” button. For my test I was using UltraGridExelExporter 3.0, also I have test it and with UltraGridExelExporter 2.0 and I was not able to get the mentioned error. My OS is Win 7 SP1, and I try to open the exported file with Excel 2007 and 2010.
Please test your scenario with the latest service release of 10.2 and if your issue still exist , please post a small sample that illustrates your issue and also give me more information about the Excel that you are using to open the exported file, your OS and the exact steps that I should follow in order to reproduce your issue on my machine.
I am waiting for your response.
One additional note... I'm not doing exports from a grid I am using the Excel.Wookbook and Excel.Worksheet objects directly...
It will be good if you are able to reproduce your issue in a small sample in order to look into it.
I am waiting for your details.
A final update. The problem was finally resolved by two changes:
1. I moved to 2010.3 with the latest patches applied. That got my small sample past the problem with setting document properties, but the warning still occurred in the production application.
2. In the application the problem was traced to clearing cell formats to “” rather than to “General”. That hadn’t been a problem in the past (with Excel itself), but it can trigger the problem with the new validation add-in…
I have created a support ticket for you with id CAS-68183-KHZQT5 in order to link your case with existing issue in our system, and when the fix is avalibe you will be notified.
Thank you.
I'm running 2151 at the moment (released on June 30th). I'll watch for something newer...
It might have something to do with the file creation. It's possible the Excel library is writing out slightly incorrect information that Microsoft Excel normally ignores because it is less strict, whereas the add-in catches these types of errors and reports them. It does sound like it might be the same bug that was fixed recently. I would recommend getting the latest SR. However, I don't believe the SR which contains this fix has been released yet. If not, it should probably be release in the next few days. Try installing that SR when it is released and let me know if you still experience the issue. Thanks.
One additional note. The patch is an Office Add-in. It wouldn't be present on the Windows 2003 Server it was tested on and shouldn't have anything to do with the file creation...