VLOOKUP bug?

The code is below and it runs against the attached spreadsheet.

The problem is that worksheet.Cells[“F6”].Value returns #REF!, however this is working properly in Excel.

Could you please investigate?

Thank you

using System.Drawing.Imaging;
using System.Text;
using Aspose.Cells;
using Aspose.Cells.Drawing;
using Aspose.Cells.Pivot;
using Aspose.Cells.Rendering;

namespace TestAspose
{
class Program
{
static void Main(string[] args)
{
Procedure19();
Console.WriteLine(“Done!”);
Console.ReadKey();
}

private static void Procedure19()
{
Workbook workbook = new Workbook(@"…\test2.xlsx");
Worksheet worksheet = workbook.Worksheets[0];

workbook.CalculateFormula(false);

Console.WriteLine(worksheet.Cells[“F4”].Value);
Console.WriteLine(worksheet.Cells[“F5”].Value);
Console.WriteLine(worksheet.Cells[“F6”].Value);
}
}
}

Hi,

I can find the issue as you have mentioned. I have logged a ticket with an id: CELLSNET-40978. We will look into your issue to figure it out soon.

Hi,


Please try the new fix: Aspose.Cells for .NET v7.3.0.6

We have fixed your issue now.

Thank you.

Thank you, it works now.

Hi,


Thanks for your feedback and good to know that your issue is resolved.

Thank you.

Sorry, I am just curious, what was the problem? Because in other cases the vlookup function worked just fine. I found it a little bit strange that in this particular case it would not work properly.

Hi,

Thanks for your posting and using Aspose.Cells for .NET.

I have added your comments in our database against the issue id:CELLSNET-40978 so that you could know the source of problem relating to this VLOOKUP bug.

We will get back to you and update you asap.

costab:
Sorry, I am just curious, what was the problem? Because in other cases the vlookup function worked just fine. I found it a little bit strange that in this particular case it would not work properly.
Hi,

It's caused by that we did not convert a Table to a range correctly in VLOOKUP function.

The issues you have found earlier (filed as CELLSNET-40978) have been fixed in this update.


This message was posted using Notification2Forum from Downloads module by aspose.notifier.