Difference between revisions of "TUFLOW Message 0040"

From Tuflow
Jump to navigation Jump to search
Line 22: Line 22:
 
* <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>
  
|discussion_page=* [[Talk:TUFLOW Message 0040|Discuss Message 0040]]
+
<br>
|link3=''
 
|link4=''
 
 
|prelink=[[TUFLOW_Message_0038|Message 0038]]
 
|prelink=[[TUFLOW_Message_0038|Message 0038]]
 
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]]
 
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]]
 
|nextlink=[[TUFLOW_Message_0041|Message 0041]]
 
|nextlink=[[TUFLOW_Message_0041|Message 0041]]
 
}}
 
}}

Revision as of 14:04, 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
Go-up.png 0xxx Messages