Forum Discussion

ecovonrein's avatar
ecovonrein
Iron Contributor
Oct 02, 2022

Excel Bug with global relative references

This is a desperate attempt to contact Microsoft, whom I seem no longer able to contact in any shape or form.  (My ability to log "service requests" as TEAMS admin has vanished.)  If any reader here ...
excel
ecovonrein's avatar
ecovonrein
Iron Contributor
Oct 03, 2022
I agree, this link describes the identical bug. However, we see the calculation tree most recently breaking in large Excels without any VBA triggering calculations. (This did not happen until most recent formula changes.) I am fairly certain that the reason our Excels are failing corresponds to the bug exhibited thru the VBA trigger, because the values that randomly pop up in those cells are simply totally implausible.
JKPieterse's avatar
JKPieterse
Silver Contributor
Oct 03, 2022
The question is, is there VBA code that runs and hence causes this issue?
  • ecovonrein's avatar
    ecovonrein
    Iron Contributor
    Oct 03, 2022

    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). 

    • JKPieterse's avatar
      JKPieterse
      Silver Contributor
      Oct 03, 2022

      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.

      • ecovonrein's avatar
        ecovonrein
        Iron Contributor
        Oct 03, 2022

        I hear you. And there is none such. We have many UDFs but they are perfectly harmless PUBLIC FUNCTION(...) AS VARIANT. I agree with you and am similarly unable to reproduce this bug other than by resorting to Application.CalculateFull. But I avoided this stuff and it is no use: the error is now with us in the regular calculation tree. We have no macros (that change cells). It is extremely scary. (I have one enterprise value hopping from 3 mio to 5 mio at random.)

         

        What is still more annoying that there appears to be no route to get Microsoft to acknowledge the bug and track progress.