R&R Version 8.1 Export problems

[Neil_Bozievich_(Guest)]

This R&R application is launched out of Visual Foxpro 6.0, and is displaying numerous data errors that are dependent on the file format selected.____ Printer Control Coded: No Problems____ ASCII Text: No Problems other than truncated some of the decimal values____ EXCEL Worksheet: Rows and Rows of data are NOT being copied to the export file, sometimes as many as 2/3^s of the data rows available____ CSV: Same problem as EXCEL Worksheet cited above____ Rich Text Format: Each separate report^s file is fine, other than the same truncation of values cited above in the ASCII Text format. However, when using Visual Foxpro to convert each file to a string value, and then concatenate the string to a single file, only the first report is evident, even though the file size indicates more should be present.____ Word Document: Pure garbage - the output is there, but when brought up into MS Word, it bears absolutely no resemblence to the reports that should have been generated.____Any assistance would be greatly appreciated !____ Neil I. Bozievich

[kfleming]

Do the same problems exist if running the reports from the report designer? 8.1 is an older release so perhaps it it time to upgrade.____Kathleen__R&R Support

[Neil_Bozievich_(Guest)]

Kathleen,____ I just finished testing one of the reports for behavior out of the report designer directly. Unfortunately, It^s behavior is exactly the same as the reports produced from the application using RRUNIN.dbf and the runtime executible with the appropriate DLL^s. The report I tested has a title, page header, page footer and a relatively simple record line, and the record line was the export source. There should have been approximately 80 records exported. I generated a file for both Excel and CSV, which both produced exactly a field column name line and a single line of data !!! One might assume that the pointer was on the last record of the table, but the record exported was the first record in the table, and why would print or preview work just fine out of the same environment ??____ Upgrading the software is not an option, as it requires money which the client is probably not willing to spend, and there are no assurances that the new version would work any better than this one. Frankly, I expect this version to perform properly, just like the version 6.0 of Visual Foxpro that the application is programmed in (both 2 versions old now). Back when I performed the original programming task, both versions were current...____ My own naive assessment is that the supporting DLL^s that perform the exports have some problems, but I would prefer that I have made some silly mistake that is preventing them from functioning properly. Any further help would be appreciated !______ Neil I. Bozievich__ (252) 473-6671

[kfleming]

If you want to email the report and data to me I will have a look and will let you know if it indeed works correctly in the latest release.____Kathleen__R&R Support__kfleming@livewarepub.com

[kfleming]

I think that the problem in the report was a little calculated field containing just a blank space character. When I replaced that calc with a literal text field of hard spaces on the layout, the export looks like it is now working.____Interestingly I saw the same export problem in both 8.1 and the latest 10.1 release.__So something about that little hard space as a calculation seemed problematic in this report.____Kathleen__R&R Support

[Neil_Bozievich_(Guest)]

Kathleen,____ First, I want thank you for working on this problem. I am sure that the change you discovered works. The only problem is the number of reports that would require this change (probably all of them). That BLANK_LINE character is a holdover from the DOS days, where it was necessary to force the report writer to print the line. For some reason, other approaches didn^t work.____ It will be up to the client whether they want to expend the money to fix this problem for all reports.______ Thanks again !____ Neil I. Bozievich