Hi I would like to know when this serious bug is going to be fixed?!? I have seen many posts saying that this behavior is deemed to have been done intentionally, and therefore will not be changed.
At the very least, can you create a new export format (or a workaround) which allows the export to abide by the suppression rules?
The problem here is that in Crystal Reports, it is possible to suppress a section, but when the resulting file is exported to csv format, the suppressed lines are included with just the separators (usually commas) included.so the output looks something like this:
"Sam Sneed","123 Mockingbird Lane","Seattle","WA","98000"
,,,,,
"Tracy Turnip","666 Neon Lane","Tacoma","WA","97987"
,,,,,
where the commas represent suppressed lines. Most of our formatting is for database uploads in the format of
Sam Sneed|123 Mocking Bird Lane|Seattle|WA|98000
where the pipe character is the separator and there is no delimiter for strings.
