Forum Discussion
Excel Bug with global relative references
ecovonrein I'm afraid this is a known bug. I have reported this decades (!) ago with no effect. I think I can safely say this bug is not going to be fixed. Here's a mention (by me) in my range names article from 2010 http://web.archive.org/web/20100625131543/http://www.jkp-ads.com/Articles/ExcelNames10.asp
My advice: Do not use range names using this structure unless there is NO VBA code triggering calculations.
- JKPieterseOct 03, 2022Silver ContributorThe question is, is there VBA code that runs and hence causes this issue?
- ecovonreinOct 03, 2022Iron Contributor
No. There is no VBA event code "onCalculate". Just plain F9, totally random errors. It is intolerable, frankly. My feeling is that the VBA trigger example is just a reliable way to highlight an underlying bug. I don't know what my spreadsheets do to provoke this bug, but it does not involve VBA macros (eg Application.CalculateFull, which I use in my demonstration).
The calculation tree does involve VBA *functions* (UDF).
- JKPieterseOct 03, 2022Silver Contributor
What do those UDF's look like? I could not reproduce a UDF to cause this bug.
However, even if there is no OnCalculate code, *any* VBA code that triggers a calculation (such as changing a cell value) will cause this bug.