This content has been marked as final. Show 4 replies
I have to load a massive set of files that uses a non-standard delimiter (umlaut char 168). Getting the provider to change delimiters is not an option.
In Expressor Desktop, when I create a new schema and select the file, everything goes fine. I can put the umlaut into the delimiter, and Expressor will recognize the field breaks in the file.
If I then try to actually run a step with Read File, Expressor fails, saying the records only have one field.
I tested my schema by converting it and the file to semi-colon delimited, and everything worked fine. SO it seems it must be something with the Read File and the custom delimiter. Any ideas?
Here's a row of sample data...
0C7C¨ABC COMPANY¨¨¨¨¨¨¨¨0C7C¨¨ ¨¨¨