CrystalMeister
Programmer
Got a situation where I keep getting the dreaded Division by Zero error when trying to export a report in TEXT type format (instead of RTF - which works fine BTW) from a legacy VB6 app calling the old Crystal API Report Engine function calls. The PC (running on Win XP Pro) has CR 10 Developers edition loaded on it and the RPT file is updated as a Crystal 10 file.
When the code hits the line that calls PEStartPrintJob, the program immediately kicks out a VB error message box Runtime Error 11: Division by Zero
I've downloaded three latest update zip files from BO download page and think that I've got the latest and greatest files on the PC. But still get the same error.
Funny thing is that 56 different RPT files that are getting created as RTF exported disk files are processed just fine with no glitches using the Crystal API calls. The one file that is filtered through as TEXT exported disk file blows up on me with this error. So I know that the legacy code works....it just seems that the U2FTEXT.DLL is corrupting the output.
Any ideas? Please share.
Thanks,
When the code hits the line that calls PEStartPrintJob, the program immediately kicks out a VB error message box Runtime Error 11: Division by Zero
I've downloaded three latest update zip files from BO download page and think that I've got the latest and greatest files on the PC. But still get the same error.
Funny thing is that 56 different RPT files that are getting created as RTF exported disk files are processed just fine with no glitches using the Crystal API calls. The one file that is filtered through as TEXT exported disk file blows up on me with this error. So I know that the legacy code works....it just seems that the U2FTEXT.DLL is corrupting the output.
Any ideas? Please share.
Thanks,