sap crystal reports runtime engine slow install

We all adopted Crystal long ago at some stage or another. Then in 2008 Business Objects was bought by SAP where it lives today.Īll of Sage 100, 300, 500 and X3 ERP use Crystal Reports as their main reporting engine. Shortly after in 2003 it was sold again to Business Objects. Eventually Seagate gave up on this and Crystal went private and independent as Crystal Decisions. The original founders then struck it rich when they sold their company to Seagate in 1994, which was trying to branch out from hard disks to software. Then they generalized the product to dynamically look at any database and that became the Crystal Reports of today.

This was originally developed as an add-in product for the MS-DOS based Accpac Plus. This project was cancelled and some of the people involved quit and started their own company to develop Crystal Reports (then Quick Reports). They started a project to have a new WYSIWYG report writer as part of the product rather than the codes based approach being used. This blog is more about the history of how ERP to Crystal integrations have gone in the past and the various challenges faced.Īccpac (now Sage 300 ERP) was originally developed by the Basic Software Group in the eighties in Vancouver.

I’ve previously blogged on customizing Crystal Reports for Sage 300 ERP (Accpac) here. I put a questionnaire on how people liked Crystal Reports up on the “ Sage Partners, Employees & Alumni Networking Group” group on LinkedIn and received a lot of good discussion.

Sap crystal reports runtime engine slow install