The Engine object represents the Monte Carlo simulation engine - its parameters include the sampling method, for example. The Solver object represents the Monte Carlo process - you call its Simulate method to perform a simulation. The Problem object represents the whole problem, and the Model object represents the internal structure of the model, which in Risk Solver is defined by your formulas on the spreadsheet. This object model is a simplified subset of the object hierarchy offered by Frontline's Solver SDK Platform, which is used to build custom applications in C/C++, Visual Basic, VB.NET, Java or MATLAB.
![api vba range.cells() api vba range.cells()](https://cdn.wallstreetmojo.com/wp-content/uploads/2021/06/VBA-Cells.jpg)
Risk Solver makes available a hierarchy of objects for describing Monte Carlo simulation problems, pictured to the right. When you include a reference in your VBA module to "Risk Solver Engine V8.0 Type Library," all of the Risk Solver objects are available - they even appear in IntelliSense prompting: And everything you can do with Risk Solver in VBA can be a part of your deployed application workbook - you need just one file RSolve32.xll, the Risk Solver Engine add-in, to run your application.
![api vba range.cells() api vba range.cells()](https://www.spreadsheetsmadeeasy.com/static/5cf6a1d6d7fccdcf75bde3eea546aca0/a8378/Feature-Image-Getting-and-Setting-Cell-Values.png)
The same power to create custom risk analysis applications is available to you through Risk Solver's VBA Object Model.
![api vba range.cells() api vba range.cells()](https://cdn.educba.com/academy/wp-content/uploads/2019/05/VBA-Range-Cells-Example-4-5.gif)
If you've used Visual Basic (VBA) to control Excel through its objects such as Worksheets, Ranges and Cells, you know how powerful and convenient this can be for creating custom applications.