TUFLOW Message 0408 - Revision history

Melissa.Moghanloo at 01:31, 22 December 2022

2022-12-22T01:31:51Z

← Older revision		Revision as of 11:31, 22 December 2022
Line 7:		Line 7:
	If the error message is triggered by a check files, delete all check files before starting the model again.		If the error message is triggered by a check files, delete all check files before starting the model again.
	<br>		<br>

	\|prelink=[[TUFLOW_Message_0407\|Message 0407]]
	\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]		\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]
	\|nextlink=[[TUFLOW_Message_0411\|Message 0411]]
	}}		}}

Pavlina Monhartova at 00:11, 26 July 2022

2022-07-26T00:11:34Z

← Older revision		Revision as of 10:11, 26 July 2022
Line 5:		Line 5:
	\|message_desc=As of TUFLOW 2013-12-AC, if a .shp file object’s .dbf record (attribute data) is flagged in the .dbf file as a deleted record this is now supported in that TUFLOW ignores the GIS object and treats it as non-existent. This enhancement arose due to QGIS Version 2.2, rather than removing the object and its attribute data from the .shp and .dbf files if it was deleted by the user, sometimes retains the data and uses the .dbf file deleted flag to mark the object as being deleted. If using TUFLOW builds prior to 2013-12-AC with QGIS Version 2.2 the presence of the .dbf deleted flag would cause TUFLOW to terminate with “ERROR 0408 - End of .dbf file encountered whilst reading record”. Prior versions of QGIS (as far as we can tell) and our testing of ArcGIS thus far indicate that these software remove the object and attribute data rather than use the .dbf deleted flag.		\|message_desc=As of TUFLOW 2013-12-AC, if a .shp file object’s .dbf record (attribute data) is flagged in the .dbf file as a deleted record this is now supported in that TUFLOW ignores the GIS object and treats it as non-existent. This enhancement arose due to QGIS Version 2.2, rather than removing the object and its attribute data from the .shp and .dbf files if it was deleted by the user, sometimes retains the data and uses the .dbf file deleted flag to mark the object as being deleted. If using TUFLOW builds prior to 2013-12-AC with QGIS Version 2.2 the presence of the .dbf deleted flag would cause TUFLOW to terminate with “ERROR 0408 - End of .dbf file encountered whilst reading record”. Prior versions of QGIS (as far as we can tell) and our testing of ArcGIS thus far indicate that these software remove the object and attribute data rather than use the .dbf deleted flag.
	\|suggestions=If you are using a version of TUFLOW prior to 2013-12-AC it is recommended that you use a later version. Exporting the shapefile into a new file may also remove the offending deleted object record.<br>		\|suggestions=If you are using a version of TUFLOW prior to 2013-12-AC it is recommended that you use a later version. Exporting the shapefile into a new file may also remove the offending deleted object record.<br>
	If the error message is triggered by a check files, delete all check files before starting the model again.~~<br>~~		If the error message is triggered by a check files, delete all check files before starting the model again.
	<br>		<br>
	\|prelink=[[TUFLOW_Message_0407\|Message 0407]]		\|prelink=[[TUFLOW_Message_0407\|Message 0407]]

Pavlina Monhartova at 00:11, 26 July 2022

2022-07-26T00:11:17Z

← Older revision		Revision as of 10:11, 26 July 2022
Line 4:		Line 4:
	\|type=[[ERROR]]		\|type=[[ERROR]]
	\|message_desc=As of TUFLOW 2013-12-AC, if a .shp file object’s .dbf record (attribute data) is flagged in the .dbf file as a deleted record this is now supported in that TUFLOW ignores the GIS object and treats it as non-existent. This enhancement arose due to QGIS Version 2.2, rather than removing the object and its attribute data from the .shp and .dbf files if it was deleted by the user, sometimes retains the data and uses the .dbf file deleted flag to mark the object as being deleted. If using TUFLOW builds prior to 2013-12-AC with QGIS Version 2.2 the presence of the .dbf deleted flag would cause TUFLOW to terminate with “ERROR 0408 - End of .dbf file encountered whilst reading record”. Prior versions of QGIS (as far as we can tell) and our testing of ArcGIS thus far indicate that these software remove the object and attribute data rather than use the .dbf deleted flag.		\|message_desc=As of TUFLOW 2013-12-AC, if a .shp file object’s .dbf record (attribute data) is flagged in the .dbf file as a deleted record this is now supported in that TUFLOW ignores the GIS object and treats it as non-existent. This enhancement arose due to QGIS Version 2.2, rather than removing the object and its attribute data from the .shp and .dbf files if it was deleted by the user, sometimes retains the data and uses the .dbf file deleted flag to mark the object as being deleted. If using TUFLOW builds prior to 2013-12-AC with QGIS Version 2.2 the presence of the .dbf deleted flag would cause TUFLOW to terminate with “ERROR 0408 - End of .dbf file encountered whilst reading record”. Prior versions of QGIS (as far as we can tell) and our testing of ArcGIS thus far indicate that these software remove the object and attribute data rather than use the .dbf deleted flag.
	\|suggestions=If you are using a version of TUFLOW prior to 2013-12-AC it is recommended that you use a later version. Exporting the shapefile into a new file may also remove the offending deleted object record.		\|suggestions=If you are using a version of TUFLOW prior to 2013-12-AC it is recommended that you use a later version. Exporting the shapefile into a new file may also remove the offending deleted object record.<br>
			If the error message is triggered by a check files, delete all check files before starting the model again.<br>
	<br>		<br>
	\|prelink=[[TUFLOW_Message_0407\|Message 0407]]		\|prelink=[[TUFLOW_Message_0407\|Message 0407]]

Melissa.Moghanloo at 01:05, 1 July 2022

2022-07-01T01:05:16Z

← Older revision		Revision as of 11:05, 1 July 2022
Line 5:		Line 5:
	\|message_desc=As of TUFLOW 2013-12-AC, if a .shp file object’s .dbf record (attribute data) is flagged in the .dbf file as a deleted record this is now supported in that TUFLOW ignores the GIS object and treats it as non-existent. This enhancement arose due to QGIS Version 2.2, rather than removing the object and its attribute data from the .shp and .dbf files if it was deleted by the user, sometimes retains the data and uses the .dbf file deleted flag to mark the object as being deleted. If using TUFLOW builds prior to 2013-12-AC with QGIS Version 2.2 the presence of the .dbf deleted flag would cause TUFLOW to terminate with “ERROR 0408 - End of .dbf file encountered whilst reading record”. Prior versions of QGIS (as far as we can tell) and our testing of ArcGIS thus far indicate that these software remove the object and attribute data rather than use the .dbf deleted flag.		\|message_desc=As of TUFLOW 2013-12-AC, if a .shp file object’s .dbf record (attribute data) is flagged in the .dbf file as a deleted record this is now supported in that TUFLOW ignores the GIS object and treats it as non-existent. This enhancement arose due to QGIS Version 2.2, rather than removing the object and its attribute data from the .shp and .dbf files if it was deleted by the user, sometimes retains the data and uses the .dbf file deleted flag to mark the object as being deleted. If using TUFLOW builds prior to 2013-12-AC with QGIS Version 2.2 the presence of the .dbf deleted flag would cause TUFLOW to terminate with “ERROR 0408 - End of .dbf file encountered whilst reading record”. Prior versions of QGIS (as far as we can tell) and our testing of ArcGIS thus far indicate that these software remove the object and attribute data rather than use the .dbf deleted flag.
	\|suggestions=If you are using a version of TUFLOW prior to 2013-12-AC it is recommended that you use a later version. Exporting the shapefile into a new file may also remove the offending deleted object record.		\|suggestions=If you are using a version of TUFLOW prior to 2013-12-AC it is recommended that you use a later version. Exporting the shapefile into a new file may also remove the offending deleted object record.
			<br>
	\|discussion_page=* [[Talk:TUFLOW Message 0408\|Discuss Message 0408]]
	\|link3=''
	\|link4=''
	\|prelink=[[TUFLOW_Message_0407\|Message 0407]]		\|prelink=[[TUFLOW_Message_0407\|Message 0407]]
	\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]		\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]

Par at 06:38, 19 August 2014

2014-08-19T06:38:16Z

← Older revision		Revision as of 16:38, 19 August 2014
Line 3:		Line 3:
	\|alt_msg=NA		\|alt_msg=NA
	\|type=[[ERROR]]		\|type=[[ERROR]]
			\|message_desc=As of TUFLOW 2013-12-AC, if a .shp file object’s .dbf record (attribute data) is flagged in the .dbf file as a deleted record this is now supported in that TUFLOW ignores the GIS object and treats it as non-existent. This enhancement arose due to QGIS Version 2.2, rather than removing the object and its attribute data from the .shp and .dbf files if it was deleted by the user, sometimes retains the data and uses the .dbf file deleted flag to mark the object as being deleted. If using TUFLOW builds prior to 2013-12-AC with QGIS Version 2.2 the presence of the .dbf deleted flag would cause TUFLOW to terminate with “ERROR 0408 - End of .dbf file encountered whilst reading record”. Prior versions of QGIS (as far as we can tell) and our testing of ArcGIS thus far indicate that these software remove the object and attribute data rather than use the .dbf deleted flag.
	\|message_desc=????
			\|suggestions=If you are using a version of TUFLOW prior to 2013-12-AC it is recommended that you use a later version. Exporting the shapefile into a new file may also remove the offending deleted object record.
	\|suggestions=????
	\|discussion_page=* [[Talk:TUFLOW Message 0408\|Discuss Message 0408]]		\|discussion_page=* [[Talk:TUFLOW Message 0408\|Discuss Message 0408]]
	\|link3=''		\|link3=''

Bill Syme at 02:15, 7 October 2011

2011-10-07T02:15:38Z

← Older revision		Revision as of 12:15, 7 October 2011
Line 10:		Line 10:
	\|prelink=[[TUFLOW_Message_0407\|Message 0407]]		\|prelink=[[TUFLOW_Message_0407\|Message 0407]]
	\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]		\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]
	\|nextlink=[[~~TUFLOW_Message_0413~~\|Message ~~0413~~]]		\|nextlink=[[TUFLOW_Message_0411\|Message 0411]]
	}}		}}

Bill Syme at 01:49, 7 October 2011

2011-10-07T01:49:48Z

← Older revision		Revision as of 11:49, 7 October 2011
Line 10:		Line 10:
	\|prelink=[[TUFLOW_Message_0407\|Message 0407]]		\|prelink=[[TUFLOW_Message_0407\|Message 0407]]
	\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]		\|uplink=[[0xxx_TUFLOW_Messages\|0xxx Messages]]
	\|nextlink=[[~~TUFLOW_Message_0421~~\|Message ~~0421~~]]		\|nextlink=[[TUFLOW_Message_0413\|Message 0413]]
	}}		}}

tuflow>Par: Created page with '{{TUFLOW_Message |tuflow_message=ERROR 0408 - End of .dbf file encountered whilst reading record. |alt_msg=NA |type=ERROR |message_desc=???? |suggestions=???? |discussion_pag...'

2010-11-30T04:47:35Z

Created page with '{{TUFLOW_Message |tuflow_message=ERROR 0408 - End of .dbf file encountered whilst reading record. |alt_msg=NA |type=ERROR |message_desc=???? |suggestions=???? |discussion_pag...'

New page

{{TUFLOW_Message
|tuflow_message=ERROR 0408 - End of .dbf file encountered whilst reading record.
|alt_msg=NA
|type=[[ERROR]]
|message_desc=????
|suggestions=????
|discussion_page=* [[Talk:TUFLOW Message 0408|Discuss Message 0408]]
|link3=''
|link4=''
|prelink=[[TUFLOW_Message_0407|Message 0407]]
|uplink=[[0xxx_TUFLOW_Messages|0xxx Messages]]
|nextlink=[[TUFLOW_Message_0421|Message 0421]]
}}