0

I have Excel 2024 (Microsoft LTSC MSO version 2408 build 16.0.17932.20496 64-bit), everything was working fine until a couple of days ago, then suddenly the Excel SolverCode module stopped working (showing a popup with "Compile error in hidden module: SolverCode" when I tried to use it).

I tried everything, but to no avail.

I opened Solver.xlam and the error is shown in the attachment.

Anyone have any ideas?

enter image description here enter image description here enter image description here

Improve this question
4
  • 1
    I could be wrong but seems like it’s a bad Office update that nuked RefEdit controls. Solver’s UI uses a RefEdit named refObj. I am guessing that the update removed/invalidated RefEdit on your system, so dlgSolverParameters.refObj.Text no longer exists and the Solver project won’t compile. Try to rollback the update and see what happens? OR Try updating Excel again. I updated Excel yesterday and the new build is 2508 Build 16.0.19127.20082 - 64-bit Excel->Account->Update Options->Update Now Commented Aug 20 at 6:56
  • 1
    MS have a habit of breaking their own code from time to time. The release of a new build so soon after 2408 suggests that they broke something badly. You can take the password protection off the solver.xlam by opening it as a zip file and a quick hack (google for it). I do that to unset the useless "Make Unconstrained Variables Non Negative" flag by default. My fitted parameters are almost always alternating signs. Commented Aug 20 at 7:07
  • @MartinBrown The "Make Unconstrained Variables Non Negative" is very handy when trying to get the Solver to calculate the number of people needed to do a real task : -2 people is not very helpful :) Commented Aug 20 at 16:25
  • @Solar Mike -2 fish was good enough for Dirac. It is a terrible default requiring a positive only parameter solution and gets lots of naive users into trouble with cannot solve constraints and/or crazy results with huge misfits. Commented Aug 20 at 18:20

1 Answer 1

Reset to default
1

Solved.

Basically, after editing my solver.xlam, I commented out every line Excel complains about (4 lines in total, each time it uses dlgSolverParameters.refObj or .refVariables). After a couple of runs, it worked, so I closed and reopened Excel (the xlam restored itself), and magically everything worked.

Thank you all.

---

EDIT: I add the password for the solver.xlam: Wildebeest!!

Improve this answer
Sign up to request clarification or add additional context in comments.

1 Comment

Turn it off and on again. The more things change...

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.