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…)
Yes, a hair under 85% of our users are on Windows XP (DoD, Defense Contractors, Suppliers). As I mentioned in the first post, it only pops up after the update is applied.
Since my last post I've also discovered that you don't even need to set any properties. A simple:
With mWorkbook.DocumentProperties End With
Will trigger the pop-up...
I don't think I was clear in what I really wanted to know. Has the problem ever occurred on a machine that was not running Windows XP? The reason I ask is a bug related to this was fixed recently but it only occurred when the Excel file was saved on a Windows XP machine. I think this issue might also be fixed by the same fix, but if you've experienced the issue on a Vista or Windows 7 machine, then it is probably not the same bug.
We have only tested creating the file under Windows XP x86 and Windows Server 2003 x64 R2. Opening it has only been done under Windows XP x86 (Office 2003 and Office 2007).
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...
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.
Hello ,
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...