I had to do some digging, but I figured out what the problem is.
The “Select to File” function in TDA 3.0 defaults to using UTF-8 encoding, even when creating a CSV file. UTF-8 encoding makes the file a binary file. There are no options when selecting “Comma separated delimited file” for any type of encoding (perhaps a future enhancement?).
I was forced to switch to using an Export template which does allow me to force a specific file encoding. Using the Export template and exporting to a comma separated text file forced to US-ASCII resolved the problem - the file is now in ANSI format by default, which is a text format.
The only issue that I’m having is that the Export Template is: A) Taking longer with the automation; and B) creates a bigger hit against the system resources.
If an option could be added to the “Select to File” when using a text file format (as CSV should be considered) that allows you to force the file encoding, that would be awesome.