Difference between revisions of "TUFLOW Message 0040"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{TUFLOW_Message | {{TUFLOW_Message | ||
| − | |tuflow_message=ERROR 0040 - No | + | |tuflow_message=ERROR 0040 - No End If specified for If Scenario. |
|alt_msg=NA | |alt_msg=NA | ||
|type=[[ERROR]] | |type=[[ERROR]] | ||
Revision as of 09:17, 20 September 2011
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
|