You were right it was due to the encoding of the text files. Some were ANSI and some were Unicode. Am I right in thinking Monarch can only deal with one coding type at a time?
The problem must have stemmed from the user changing the coding during download from the system. The problem is working out which files are coded in which type without opening each one in notepad - I've just used the size of the file as a guage. It was much easier in Monarch V8 as you would have seen the difference in the report files on screen!
On this occasion I've just made two exports but will have to make sure the source files are the same coding in future.
You were right it was due to the encoding of the text files. Some were ANSI and some were Unicode. Am I right in thinking Monarch can only deal with one coding type at a time?[/b][/quote]V9 has some additonal capability to deal with Unicode files - so yep, it would probably not reject them or hightlight the difference.
Can't answer your question technically but I would not be surprised if handling both types was concurrently was a tad tricky.
Can you 'fix' the user download process to make it more consistent? My gut feel is that to do so would be a good move for future interactions anyway.