Downloadomronplcpassword13 Note that a single digit (e.g. 0) before a sequence of dashes (-) will turn the sequence into a fixed length field. Thus, Some text--with-subsequent-sequence-of-dashes-in-field-1 Will be treated as a zero-width-space, causing it to appear to be part of the next field: Some text-with-subsequent-sequence-of-dashes-in-field-2 In other words, by designating a field as fixed length, the error cannot occur when the number of characters in the field exactly matches the specified length. Since it won't be possible to mess up the number of characters within a field no matter how poorly you write your data, it won't occur often enough to even be a concern. It is possible for a field with this property to be accidentally created, but I can't think of any circumstances in which this would happen. A: The dash (dash) is the (2-character) specific "end of quoted text" character, so if a field contains a dash, the client should consider it the end of quoted text. A: When extracting data from a file, you can tell your file parser to either extract every value or extract every field. If you extract every value, any value containing a leading dash - is an error. If you know a quoted string is enclosed between a pair of quotes, you can always make it a fixed length field by escaping the dash in the value using double quotes. 1st field: This text is ok "This is ok" - This is the line of text that starts a string 2nd field: 1st line: "This is ok" 2nd line: This is the line of text that starts a string 3rd field: 1st line: This is the line of text that starts a string 2nd line: "This is ok" Note that the line starting "This is ok" is in the 2nd field. That is because it's enclosed in quotes (this is like escaping the dash -), meaning it should be treated as a fixed length field. Another way to control field length is to escape it with backslashes (\). 1st field: This is ok "This is ok" - This is the line of text that 1cdb36666d
Related links: