I am QA'ing the 7.1.0.5 version of .Cells with our application. We are having a problem with one particular named range in on a sheet that comes from an XLS file imported into a workbook using the Combine function.
The file Cash_Flow_Float.xls contains a single sheet called Float that defines a number of named ranges. The failure I'm looking at is in Checks_Cleared_in_Period which has Workbook scope in this file.
QA__Cash_Flow_V10.xlsx is the output from a previous version of .Cells. You can see that in this workbook there is a Float worksheet, and on it is the named range Checks_Cleared_in_Period that points to the correct range at Workbook scope.
QA__Cash_Flow_V11.xlsx was generated with the latest .Cells. If you look at the Float sheet, you'll see that the named range does not exist. However, if you look at the first worksheet, Graphs, you'll find the named range there, though it does point to the correct cells on the Float sheet. This named range appears to have had its scope changed from Workbook to the Graphs sheet. There is another named range, Float, that has also been changed to Graph scope, but not that there are also named ranges that haven't been changed, such as Float_Start_Date.
If it matters, the Graphs sheet happens to come from our template file, and is the only sheet in that file. All other sheets are either generated by our application or come from other XLS files using Combine.
You can see a use of the broken named range on 'CF All Segments':B86. (You have to expand the group to see this cell.) It expects to find the named range on the Float sheet (or at workbook scope.)
This is a show-stopper bug for us in terms of deploying the latest .Cells.
Thanks for your attention.
--Howard