UPDATE TO THE BELOW
The update has now rolled out to lots of machines, and broken maybe 90% of the work we have done in the past. Just to clarify exactly what I mean:
Using VBA (or C# or anything else for that matter) - we dynamically insert formulas at runtime using named ranges. For example:
=(MIN(Bid_S1,Bid_S2, Bid_S3, Bid_S4, Bid_S5)/Bid_S3)*PriceWeighting
This now longer works and gives a SPILL error. When I try to put the @ in front as suggested, I see a message telling me @ is not supported for some versions of Excel, do I still want to use it.
Option 1 - yes, I put @'s in front of every named range, spill error.
Option 2 - the formula they suggest is identical to the one I already had. Same Spill error.
This is going to be a huge problem for a lot of companies, surely.
Hard not to agree with this question:
https://answers.microsoft.com/en-us/msoffice/forum/all/the-new-dynamic-arrays-spill-functionality-should/92f9847f-deca-4ec9-ada3-9e005a5b68da?rtAction=1579696000111&page=1
A very bizarre situation. 4 different computers. Each running identical versions of Excel, Windows.
A simple named range with 4 cells say, called PlanID
PlanID
1
2
3
4
Type "=PlanID" next to the first, on 3 of the machines it returns 1, as I would expect. On the 4th machine it returns the formula array of the whole range. Just spent about 2 hours researching Spill errors etc but nothing seems to directly relate to the 2 issues I have:
- How can something that has worked reliably for years suddenly not work
- Why only on one machine?
Literally identical versions of Excel (16.0.12325.20280 32 bit)