Difference between revisions of "TUFLOW Message 0004"
(Created page with "{{TUFLOW_Message |tuflow_message=ERROR 0004 - Could not access save date of "filename" to check with "filename.tab" |alt_msg=NA |type=ERROR |message_desc=When working with Ma...") |
m |
||
| Line 5: | Line 5: | ||
|message_desc=When working with MapInfo files, by default TUFLOW checks the save date of the MapInfo export files (.mif or .mid) which TUFLOW reads, and the MapInfo propriety format that TUFLOW is unable to read. This is useful as it prevents an older version of the file from being read, i.e. it prevents you from modifying a file in MapInfo and forgetting to export it. However, if the corresponding MapInfo .tab file does not exist the error is reported. | |message_desc=When working with MapInfo files, by default TUFLOW checks the save date of the MapInfo export files (.mif or .mid) which TUFLOW reads, and the MapInfo propriety format that TUFLOW is unable to read. This is useful as it prevents an older version of the file from being read, i.e. it prevents you from modifying a file in MapInfo and forgetting to export it. However, if the corresponding MapInfo .tab file does not exist the error is reported. | ||
|suggestions=This check can be suppressed by including the following command in the .tcf:<br> | |suggestions=This check can be suppressed by including the following command in the .tcf:<br> | ||
| − | <tt>Check MI Save Date == OFF </tt><br> | + | <font color="blue"><tt>Check MI Save Date </tt></font> <font color="red"><tt>== </tt></font><tt> OFF </tt><br> |
This is often encountered if a model has been copied, without the MapInfo files. Another option is to import the .mif / .mid files into MapInfo and then immediately re-export them, importing the files ensure that MapInfo .tab file exists, re-exporting ensures the .mif file has a later save date than the .tab file. | This is often encountered if a model has been copied, without the MapInfo files. Another option is to import the .mif / .mid files into MapInfo and then immediately re-export them, importing the files ensure that MapInfo .tab file exists, re-exporting ensures the .mif file has a later save date than the .tab file. | ||
|discussion_page=* [[Talk:TUFLOW Message 0004|Discuss Message 0004]] | |discussion_page=* [[Talk:TUFLOW Message 0004|Discuss Message 0004]] | ||
Revision as of 14:08, 25 June 2015
TUFLOW Message
ERROR 0004 - Could not access save date of "filename" to check with "filename.tab"
Alternate Message
NA
Message Type
ERROR
Description
When working with MapInfo files, by default TUFLOW checks the save date of the MapInfo export files (.mif or .mid) which TUFLOW reads, and the MapInfo propriety format that TUFLOW is unable to read. This is useful as it prevents an older version of the file from being read, i.e. it prevents you from modifying a file in MapInfo and forgetting to export it. However, if the corresponding MapInfo .tab file does not exist the error is reported.
Suggestions
This check can be suppressed by including the following command in the .tcf:
Check MI Save Date == OFF
This is often encountered if a model has been copied, without the MapInfo files. Another option is to import the .mif / .mid files into MapInfo and then immediately re-export them, importing the files ensure that MapInfo .tab file exists, re-exporting ensures the .mif file has a later save date than the .tab file.
| Up |
|---|
 0xxx Messages
|