My load statement uses a delimiter in a load statement for a file with a combo of '^~', however, it only seems to be reading the first character '^' and then reads the field from there with the '~' character as the first one for each field. Can QVW not use more than one character as a delimiter in a load statement? I saw in the QVW reference manual an example using '\t' as a delimiter.
Thanks, but not helpful. What would you suggest I use for a delimiter as the .dat files I'm reading will have all the character sets found in an SQL statement. Using combinations of obscure characters seems to have been the answer.
I went through this excercise as well but in my case I was reading CSV files. What I did was that I replaced my delimiter (|-pipe) to an underscore in the data before I wrote the CSV file. Then wrote CSV file with the pipe delimiter and used the same delimiter in QV.
Not sure what you should do. You would need to find a character somehow which is not supposed to be in use, I guess. Can you change the data, like I did, before the dat files are written?
... no, as all character sets that are in a SQL statement are present... we are looking to convert the .dat files to XML... so that may be a viable solution.
Well, in that case, when you convert dat to xml, you may want to get rid of all occurences of the character you plan to use a delimiter. What I am doing is checking each field of each record for that character, and replacing it with underscore, before the record gets written in the csv file with the delimiter. Not the best solution, but it works. Good luck.
Let me know if you find anything better to handle this situation.
