Solver.xlam 2010

  

May 28, 2014 We install Office 2010 and the Dutch MUI together. The default language is English. The problem is that the Excel Add-ins do not install in a seperate. Mar 28, 2017 Hi Anil, I notice the issue is related to the VBA editor practice. This forum focuses on general discussion about Office 2010. To better resolve your issue.

Trying to use the Analysis and Solver add-ins. By selecting File/Options/Add-ins/Manage./Go then ticking 'analysis', the Analysis add-in moves from the 'inactive' to the 'active' list but doesn't then appear in the Data tab.

If I tick 'solver' I get an error box telling me that it cannot access the solver.xlam file (and the Solver add-in stays in the inactive list). The xlam file does exist in the right location.

Solver.xlam 2010

Trying to add other add-ins gives the same result. Nothing added-in! I saw one suggestion of an add-in installer bug.

Solver

My%windows% folder is not 'C: WINDOWS' but C: WINDOW2. However a registry search for the wrong CLSIDs didn't find anything.

Hello All, We are looking for the help on the below mentioned query. In one of the application we are using the SOLVER add-in for the linear programming calculations. So, Each time we need to add the SOLVER add-in manually or through macro(without password for the VBA editor) then it will work.

But the criteria is, Our Tool is password protected in VBA editor due to some confidential calculations in the coding. We cannot share the password to every user instead the SOLVER add-in has to add automatically into the tool. I appreciate your valuable solution for my query. Hello Anil, According to your description, you could load the add-in through macro. In my opinion, protecting or unprotecting would not cause the difference. Does the add-in fail to load if you protect the macro? If so, what code do you use to load solver add-in?

Please visit to see how to load add-ins at runtime. Regards, Celeste MSDN Community Support Please remember to click 'Mark as Answer' the responses that resolved your issue, and to click 'Unmark as Answer' if not.

This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact. Hello Anil, Have your issue been resolved? We would appreciate if you could share your solution here and I suggest mark your solution as answer to close the thread. If you issue persists, I suggest you share sample code here then we could test if we could reproduce your issue. Regards, Celeste MSDN Community Support Please remember to click 'Mark as Answer' the responses that resolved your issue, and to click 'Unmark as Answer' if not.

What Is Solver Xlam

This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact. Hello Celeste, I used the below mentioned code to add the Solver add-in Note: 1. Below code works only in some systems but not in all systems. If VB Project is unprotected then this works in all systems. '.

Dim chkRef As VBIDE.Reference Dim BoolExists As Boolean For Each chkRef In vbProj.References If chkRef.Name = 'Solver' Then BoolExists = True GoTo step1 End If Next vbProj.References.AddFromFile Application.LibraryPath & ' SOLVER SOLVER.XLAM' step1: DoEvents If BoolExists = True Then MsgBox 'Solver already exists' Else MsgBox 'Solver Added Successfully' End If '. Best Regards, Anil. Hello Celeste, Still the issue is not solved and here i am sharing the code which i used in my project. I used the below mentioned code to add the Solver add-in in VB project. Below code works only in some systems but not in all systems. If VB Project is unprotected then this works in all systems. '.

Dim chkRef As VBIDE.Reference Dim BoolExists As Boolean For Each chkRef In vbProj.References If chkRef.Name = 'Solver' Then BoolExists = True GoTo step1 End If Next vbProj.References.AddFromFile Application.LibraryPath & ' SOLVER SOLVER.XLAM' step1: DoEvents If BoolExists = True Then MsgBox 'Solver already exists' Else MsgBox 'Solver Added Successfully' End If '. Best Regards, Anil. Hello, Are you developing an Excel add-in (.xlam)? If the project is protected, does the code would fail in all system? Do you get any error when it doesn't work? Here are my steps but I fail to reproduce your issue. I am using Win10/ Excel 2016.

1.Create an xlam add-in 2.Create a subroutine called test to add Solver add-in as reference. Sub test Dim chkRef As VBIDE.Reference Dim BoolExists As Boolean Set vbProj = ActiveWorkbook.VBProject For Each chkRef In vbProj.References If chkRef.Name = 'Solver' Then BoolExists = True GoTo step1 End If Next vbProj.References.AddFromFile Application.LibraryPath & ' SOLVER SOLVER.XLAM' step1: DoEvents If BoolExists = True Then MsgBox 'Solver already exists' Else MsgBox 'Solver Added Successfully' End If End Sub 3.Protect the add-in. 4.Load the add-in in new workbook 5.Call the subroutine, it could successfully add Solver add-in as reference for the new workbook. So how do you declare vbProj? Which workbook you want it to add Solver add-in as reference? If you add reference to the protected workbook(the xlam), of course it would fail. I suggest you load the add-in using the following code in your project.

Dim myAddIn As AddIn For Each myAddIn In AddIns If myAddIn.Name = 'SOLVER.XLAM' Then myAddIn.Installed = False myAddIn.Installed = True MsgBox 'Solver Added Successfully' End If Next Regards, Celeste MSDN Community Support Please remember to click 'Mark as Answer' the responses that resolved your issue, and to click 'Unmark as Answer' if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact. Hello Celeste, We are trying to add the Solver Add-in in Thisworkbook.

When we run with protected VB project then, only in some systems we will get this below mentioned error. (Unfortunately i am not able to attach the error image so added the error text). Compile error in hidden module: Module Name. This error commonly occurs when code is incompatible with the version, platform, or architecture of this application. Click 'Help' for information on how to correct this error. Hello, According to the error, please visit A protected contains a compilation error. Because the error is in a protected module it cannot be displayed.

This error commonly occurs when code is incompatible with the version or architecture of this application (for example, code in a document targets 32-bit Microsoft Office applications but it is attempting to run on 64-bit Office). So I test the code above with Office2016 32bit and Office2010 64bit. 1)Develop the add-in in Office2016 32bit and load in Office2010 64bit. 2)Develop the add-in in Office2010 64bit and load in Office2016 32bit. It works fine. Please check your office platforms and see in which scenario it could not work.

And please comment out other code, test the code snippet of adding reference only. Regards, Celeste MSDN Community Support Please remember to click 'Mark as Answer' the responses that resolved your issue, and to click 'Unmark as Answer' if not. This can be beneficial to other community members reading this thread.

If you have any compliments or complaints to MSDN Support, feel free to contact. Hello, I failed to reproduce the issue in Office2010 32bit. I create the add-in in Office2010 32bit and it works fine in Office2010 64bit and Office2016 64bit. I think your other code causes the issue. Please follow my steps above to test in your environment.

Regards, Celeste MSDN Community Support Please remember to click 'Mark as Answer' the responses that resolved your issue, and to click 'Unmark as Answer' if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact.

If VB Project is unprotected then this works in all systems. Do you mean you copy the unprotected workbook to all the systems or you unprotect the workbook in the non-worked system? For a non-worked computer, if you unprotect the workbook, and run the code, will you get any error alert?

See more on stackoverflow

If the versions for Office 2010 64 bit are different, I would suggest you migrate the Office 2010 64 bit to the same version to check whether it will work. MSDN Community Support Please remember to click 'Mark as Answer' the responses that resolved your issue, and to click 'Unmark as Answer' if not.

This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact. But remember its not with all 32 bit systems or not with all 64 bit system To narrow down this issue, I would suggest you compare the differences between worked and non-worked system like Office version number. MSDN Community Support Please remember to click 'Mark as Answer' the responses that resolved your issue, and to click 'Unmark as Answer' if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact.

   Coments are closed