Import Data bug?
Posted: 04.08.2009, 07:17
The data import procedure acts on standard row/column separators even when they are enclosed in quotes.
For instance, if a text field enclosed in quotes includes a carriage return, it is treated as the end of the row and the rest of the column after the carriage return is treated as the first column in the next row, thus causing any errors on the import.
Same thing happens if the specified separator character is found in a text field enclosed in quotes, such as a semi-colon or a comma.
Pete
For instance, if a text field enclosed in quotes includes a carriage return, it is treated as the end of the row and the rest of the column after the carriage return is treated as the first column in the next row, thus causing any errors on the import.
Same thing happens if the specified separator character is found in a text field enclosed in quotes, such as a semi-colon or a comma.
Pete