CSV Export Bug

Hello,
I have a report that displays data from SQL Server, and it also has a
subscription that exports the report as a CSV file to a network share on
specified schedule. There is another external app that picks up the CSV file
and imports it into a proprietary database.
The report uses a stored procedure on the SQL Server to query data that is
displays on the report. When the query returns data, everything works well.
However, there are times when there is no data returned from the query (an
empty result set). If that happens, the report itself looks fine, but the
exported CSV is messed up. When I open up the exported CSV into a text
editor, all it shows is "table1". I am not sure where its getting "table1"
from, but logically, if there is no data to be reported, I would expect the
CSV to contain the headers (field names) and no data. Obviously, the
external app that imports this CSV is not smart enough to recognize that
"table1" means no data and the entire import process crashes.
If there are any workarounds or hot fixes for this bug, I would like to find
out about them ASAP since this is a production system.
Thank you,
MHAROONNo replies, so do I assume that no one else has run into this issue? This is
a pretty serious issue for us, so I would appreciate any help.
"mharoon" wrote:
> Hello,
> I have a report that displays data from SQL Server, and it also has a
> subscription that exports the report as a CSV file to a network share on
> specified schedule. There is another external app that picks up the CSV file
> and imports it into a proprietary database.
> The report uses a stored procedure on the SQL Server to query data that is
> displays on the report. When the query returns data, everything works well.
> However, there are times when there is no data returned from the query (an
> empty result set). If that happens, the report itself looks fine, but the
> exported CSV is messed up. When I open up the exported CSV into a text
> editor, all it shows is "table1". I am not sure where its getting "table1"
> from, but logically, if there is no data to be reported, I would expect the
> CSV to contain the headers (field names) and no data. Obviously, the
> external app that imports this CSV is not smart enough to recognize that
> "table1" means no data and the entire import process crashes.
> If there are any workarounds or hot fixes for this bug, I would like to find
> out about them ASAP since this is a production system.
> Thank you,
> MHAROON