Hi. I'm having a problem exporting a report's data to Separated Values format. If anybody has any advice on how to get around this 'limitation', I'd greatly appreciate it.
I have a report that is written to be exported to text format. It is actually a data extract that will be imported into another system. I am not using Crystal's Plain Text export because its pagination causes more problems for my report than it fixes. So my only other option is exporting to Separated Values and renaming the export file extension to ".txt". I am not using any delimiters for this format (comma, tab, etc) because the extract fields are required to be in fixed positions in the file.
I have one line of data in the report header, numerous records in the details section, and one line of data in the report footer. Here is the problem I'm having. The separated values export appends the information in the report header to the beginning of every detail record, and the information in the report footer to the END of every detail record. I found a way to work around the report header problem with this article on the Business Objects site: However, it requires registry changes which is NOT ideal. Plus after making the adjusments recommended in the article, there is still one remaining nagging little issue. The information in the report FOOTER is still being appended by the export to the end of the last detail record instead of on its own line at the very end of the report. The last line in the export is meant to read //EOF (for End Of File) which is a flag for the system being imported into. The "//EOF" however is being appended to the end of the last detail record. I've tried many different variations on the article at the link above to resolve this but none have worked so far. So this export has problems. One can be resolved through a not-so-great work-around in the article above. But even that leaves this one flaw preventing it from being fully implemented, unless I can find a way to get the report footer to export in its proper place.
This problem isn't the most exciting issue to try and resolve, but if anybody has any suggestions on:
a. addressing these problems without having to make the registry changes in the above article, or if that doesn't work...
b. to get around the report footer being appended to the end of the last detail record.
Thanks a lot!
Chris
I have a report that is written to be exported to text format. It is actually a data extract that will be imported into another system. I am not using Crystal's Plain Text export because its pagination causes more problems for my report than it fixes. So my only other option is exporting to Separated Values and renaming the export file extension to ".txt". I am not using any delimiters for this format (comma, tab, etc) because the extract fields are required to be in fixed positions in the file.
I have one line of data in the report header, numerous records in the details section, and one line of data in the report footer. Here is the problem I'm having. The separated values export appends the information in the report header to the beginning of every detail record, and the information in the report footer to the END of every detail record. I found a way to work around the report header problem with this article on the Business Objects site: However, it requires registry changes which is NOT ideal. Plus after making the adjusments recommended in the article, there is still one remaining nagging little issue. The information in the report FOOTER is still being appended by the export to the end of the last detail record instead of on its own line at the very end of the report. The last line in the export is meant to read //EOF (for End Of File) which is a flag for the system being imported into. The "//EOF" however is being appended to the end of the last detail record. I've tried many different variations on the article at the link above to resolve this but none have worked so far. So this export has problems. One can be resolved through a not-so-great work-around in the article above. But even that leaves this one flaw preventing it from being fully implemented, unless I can find a way to get the report footer to export in its proper place.
This problem isn't the most exciting issue to try and resolve, but if anybody has any suggestions on:
a. addressing these problems without having to make the registry changes in the above article, or if that doesn't work...
b. to get around the report footer being appended to the end of the last detail record.
Thanks a lot!
Chris