Through my years of support for Crystal Reports I noticed that often, users seeking support will leave out basic information about their issue, potentially leading to significant delays in receiving an accurate resolution. The following guidelines apply to phone support as well as when posting you queries to the Crystal Reports / BOE developer forums, though the general ideas such as product version and detailes of error messages will apply to any software support.
1) Before even looking for support, see if you can resolve the issue by searching SCN for KBAs, Blogs, Wikis, etc. Use the search box in the top right corner of each SCN page:
See the blog My tips on searching knowledge content the SCN
2) See if you can find helpful documentation at the SAP Help Portal
3) Apply the most recent service packs.
4) Read and follow the SCN Rules of Engagement
5) Basic information you always want to provide:
- What soiurces of information did you use from your searches in step (1)
- Version of Crystal Reports or BOE used in your development project
- The SDK used in your project. Possible SDKs are:
- SAP Crystal Reports, developer version for Microsoft Visual Studio
- Crystal Reports for Eclipse (Java)
- WIN APIS for Crystal Reports (up to version 9 of Crystal reports)
- Report Designer Component (RDC) (up to version 11. 5 of Crystal Reports)
- OCX (up to version 8.5 of Crystal Reports)
- VCL for Delphi (up to version 11. 5 of Crystal Reports)
- The development language and the version of the development language. For example, MS Visual Studio .NET 2008. Crystal Reports is supported with a number of development languages. See the platforms.txt file associated with your version of Crystal Reports.
- The database you are connecting to.
- The database connection type (OLE DB, ODBC, etc.).
- Does the application work on your development computer?
- Does the actual report do what you want it to do in the Crystal Reports Designer?
- Specify the error (if applicable). A sreenshot of the error is often not a bad idea.
- If there is no error, be clear in symptom / behavior description.
6) Limit your assumptions. For example, if you are suspecting a memory issue when using CR 2008, do not assume that a note on memory leaks for CR 9.1 applies to CR 2008. Do not assume that a memory leak with one Crystal Reports SDK directly applies to another Crystal Reports SDK.
7) Do realize that a particular error can be caused by a number of underlying causes. These may depend on a number of variables from version of your product, to the database used to the printer driver used to the Service Packs used (OS Service Packs, development language Service Packs, Crystal Reports / BOE Service Packs) and more.
8) Do not ask for support if you are using a product created by a 3rd party. E.g.; if you purchased an application that displays Crystal Reports from Acme rUs Development and the application does not work, use Acme rUs Development for your first line support. It is very hard to determine the cause of an issue if we don’t even know what SDK the 3rd party developer used, or how the SDK is implemented.
9) If you are the QA tester of an application that uses Crystal Reports developed on your site by your developer, collect as much information about how the developer implemented the solution as you can before seeking support.
Following the above general guidelines should result in quicker resolution times for your issues as well as less frustration for all concerned.
Last note. Remember, phone support is available. Some issues just simply do not lend them self’s to on line resolutions. Or, your project may be in a time critical stage and getting phone support will be way quicker than any on line support. If you decide that phone support is the way for you, go to this link for directions, etc.: