Constraints can be linear, nonlinear, or constant (in special situations):
Linear constraints are more efficient in generating feasible solutions to try. They are evaluated by OptQuest before a solution is generated.
Nonlinear constraints are evaluated by Microsoft Excel before a simulation is run. They may be slower to evaluate if they contain many Microsoft Excel functions or refer to many formulas in the spreadsheet. They are less efficient at generating feasible solutions.
Constant constraints are generally an error unless a user-defined macro or the Crystal Ball Auto Extract feature is used to set values in a referenced spreadsheet cell. For more about user-defined macros and constant constraints, see information about the OptQuest Developer Kit in the Oracle Crystal Ball Developer's Guide.
When you create a constraint, its type is displayed after the formula.