Skip to Content
0
Feb 21, 2009 at 12:45 AM

DTW suggestion

17 Views

I have a suggestion to make that could make DTW a much better tool to use. It has to do with the way engine handles quotation marks ( " ) and comma at runtime.

Problem lies in the fact that the code seems to "tolerate" the use of quotation marks enclosing the string values, but seems to remove the quotation marks at runtime. Consequentely, any comma placed in the middle of a string value might cut this string in two parts, resulting in strange behaviors during imports (second part of the strings endup in next field, if it doesn't violate any rule).

When using Tab as a delimiter (.txt files), strangely enough, the code adds the shileds (quotation marks) to protect the string from being cut, and just leaves them there resulting into quotation marks being posted to the database.

Solution is simple. When we do shield our string ourselves, kindly leave the quotation marks (the protecting shields) there at run time to prevent the string from being cut, and as a bonus, try to remove them prior committing the record to database under any file format scenario (including tab delimited text files).

Thanks

Edited by: Charles G. Couturier on Feb 21, 2009 1:46 AM