I have been using Crystal 8.5, 9, 10, and 11 for years but now Office 2016 is cause MAPI issues so I need to fine a new solution. I have a large customer base who have many custom reports using the above versions. We generate report and Exports including PDF, Excel, etc. My native programming language is Delphi 5, Xe7. The MAPI problem specifically happens when the user tries to export a PDF twice from CR11 when Office 2016 has been installed.My plan was to create a print engine, that my original program would call, using VS 13/15 Express to run CR 2013 and run reports previously written with one of the above.When I try to open a report which uses dBase Files, I receive this message. I have tried all version of dBase files a few of the open but none open which have a memo field in them.(See attached file.) 'Database Connector Error:' and lots of oriental letters.I have also tried creating a new report with dBase files and all fail.Suggestions????Thanks Tony Nasca, Dove Net Software.Don't laugh. (I know this is old technology.).
In my test app for parameters it has the drop down list to get various report object info.Look at this routine: case 'Summary Fields':It lists the info and you can write the info. Use that to mark if the reports been updated.There are other ways as well, write to a database field etc.Using private void btnSaveReportAsClick(object sender, System.EventArgs e) you can save the report into a new location or exporting to RPT format will also save the updated info, along with the data.Search for ReplaceConnection, there is a KBA/DOC on how to that Ludek wrote using my code.Don. 0. So we have the converting the xBase connection to ADO and we have the report saving to a new location.The issue now is speedwhen the system is looping through the xbase tables, it is taking 10 minutes per table and sometimes there are 3 - 5 tables in the report to convert.it does complete just very slow.then when we execute the codecrViewer.ReportSource = reportDocument;crViewer.RefreshReport;the refeshreport takes 15 minutes to execute and then the system presents the report.see a picture of the machine while the system is doing the refesh. Donhere is a link to a zip filein the zip file root folder proposal1.rpt is the original report with xbase files witten by crystal 8.5.in the converted folder is proposal1.rpt converted with ADO files.in the code.txt is the code that I am using and it pretty much follows the code that you gave us.We are using the.saveas to save the file to the convertedproposal1.rpt.
We did not find an export function to save the report.When we run the bottom part of the code to view the report, it still takes 7 minutes to come up.If I open the report with crystal reports 2013, and say view, it takes 5 minutes to come up.When i save the report to convertedproposal2.rpt, and then open the proposal2.rpt and view the report it comes up immediately.So crystal report must be doing an additional convertion that is saved when we save the report to proposal2.rpt.Any suggestions?in the zip file i also included the dbf files.One note. When I try to create a new report with crystal 2015, and try to load directly a ADO Dbase 5, dbf file. It takes a few minutes to register each dbf.Any comments?. Hi Tony,Thank you for the reports.
I see why it's taking so long now. Using the Proposal1.rpt your tables are not linked, CR has always required them to be linked. When converting you should have noticed this if you clicked on the Links tab:when you click OK you get this message:You can't see it any more because of the DB type, which is also a problem because DAO is also not supported to DBF but that's a different issue.