Difference between revisions of "TUFLOW Message 0040"
Jump to navigation
Jump to search
Melissa1987 (talk | contribs) |
Melissa1987 (talk | contribs) |
||
| Line 21: | Line 21: | ||
* <font color="blue"><tt>Start 2D Domain </tt></font><font color="red"><tt>== </tt></font> | * <font color="blue"><tt>Start 2D Domain </tt></font><font color="red"><tt>== </tt></font> | ||
* <font color="blue"><tt>Define Event </tt></font><font color="red"><tt>== </tt></font> | * <font color="blue"><tt>Define Event </tt></font><font color="red"><tt>== </tt></font> | ||
| − | |||
<br> | <br> | ||
|prelink=[[TUFLOW_Message_0038|Message 0038]] | |prelink=[[TUFLOW_Message_0038|Message 0038]] | ||
Revision as of 14:05, 1 July 2022
TUFLOW Message
ERROR 0040 - No End If specified for If Scenario.
Alternate Message
NA
Message Type
ERROR
Description
No End If command was found to close of the If Scenario == block.
Suggestions
Add the End If command where it is missing.
Tip: When using commands such as If Scenario == indent the commands within the block that follows as this makes it much easier to interpret which commands apply to which event definition. For example:
If Scenario == 1974
- Read GIS Z Shape == mi\2d_zsh_road_remove.mif
Else If Scenario == exg | OpA
- Read GIS Z Shape == mi\2d_zsh_road_exg.mif
Else If Scenario == OpB
- Read GIS Z Shape == mi\2d_zsh_road_OpB.mif
End If
Other examples of commands that benefit from indenting are:
- Start 2D Domain ==
- Define Event ==
| Up |
|---|
 0xxx Messages
|