Kiran,

I know that there has been an issue that was addressed for the excel engine that resulted in a similar exception.  As such if you are still seeing this, you should test with the latest service release.  If you are using the latest service release and still see the issue then we would need an excel file that reproduces the exception.

Let me know if you have any questions with this matter.

Hi Alan

  thanks for the reply. Can you confirm the issue is fixed after the release v10.1 version of Infragisctics. B'couse if we decide to move to the next version, have to plan lot of regression testing to make sure our current functionalilty or intact. Pls confirm ASAP. We need to address this issue at the earliest.

Thanks

-Kiran

Kiran,

There was an issue resolved that was similar though I don't know if it is the same issue.  I would need a sample from you that demonstrates the same issue to determine that.  If you provided a full stack trace I may have a better idea if you provide a full stack trace.  You could install the service release on one machine and test it yourself on a copy of your application and if it doesn't resolve the issue, then you could uninstall the service release.

Let me know if you have any questions with this matter.

Hi Alen

 Here I am attaching the screen shot of Exception from VS 2010 & the excel sheet I am trying to load.

This is the code which is breaking

CurrentWorkbook = Infragistics.Excel.

Workbook.Load(excelFileStream);

I opened the existing xls file which uploads successfully & copied the contents to new file & saved it as xlsx file. That is when I see the error.

Thanks

-Kiran

Hello kiranguptha,

I ran the latest service release version for 2010 Vol 1 and resolves the ArgumentOutOfRangeException when loading the excel file. To download the latest service release can be found in My Keys & Downloads page.

Let me know if you have any questions with this matter. Thank you.

Attached one more file

Thanks

-Kiran

Hi

  We are facing lot of issues with the patch version you guys provided. We found these in Production & had to revert back (Took lot of heat from users). Pls provide me only excel fix. We don't want anyother changes.

I ahve attched the issues file. since I can attach only 200 MB. I wil raise one more post & attach another file.

thanks

-Kiran

Hi

  Thanks for the reply. I figured it out the same.

-Kiran

Hello Kiran,

I have been looking into the modified sample and I can say that this behavior is expected and is by design. I can suggest you loop through the FilterRecords collection items and check whether they have conditions. This way you will be able to know how many active filter are applied to the XamDataGrid. You can do something like this:

int count = 0;
foreach (var item in xamDataGrid1.FieldLayouts[0].RecordFilters)
{
    if (item.Conditions.Count != 0)
    {
        count++;
    }
}
MessageBox.Show(count.ToString());

Hope this helps you.