Data Access Worldwide Knowledge Base
Article ID 2005 Article Title PROBLEM: Exporting Report to MS Word using MAPI in Crystal 9 and above Article URL http://www.dataaccess.com/kbasepublic/kbprint.asp?ArticleID=2005 KBase Category CRYSTAL REPORTS Date Created 05/07/2004 Last Edit Date 05/18/2004
Article Text
PROBLEM:
I am using Visual DataFlex 9.1 and Crystal 9 and trying to export a report to Microsoft Word format using MAPI destination -- i.e. send an email with the report in Word format as an attachment.
If I use the other format options (e.g. text), it works and the email is sent with the .TXT file enclosed without problems. However, if I set the destination to MAPI and the export file format to MS Word, errors occur.
Using Crystal 8.5 the problem did not occur. Do you have any idea what the problem is?
SOLUTION:
The dll (and internal structures) used for exporting has changed in Crystal Reports 9. Unfortunately, the CrystalReport.pkg uses hardcoded dll names for exporting. This is a known issue with CRW9 and up.
The attached file contains a new subclass. The subclass doesn't support all new types (no HTML and destinations & no App, Notes, Post or VIM). Very little testing has been done, but this file is available as a beta package in order to help developers until the fix is incorporated into the product.
Be aware that this is NOT a fully tested or supported file.
Contributed By:
Ulbe Stellema
Company: Data Access Worldwide
email: ulbe.stellema@dataaccess.eu
Web Site: http://www.dataaccess.eu
Web Links Related to this Article
File cCrystalReport.pkg
URL=http://www.dataaccess.com/KBasePublic/Files/2005.cCrystalReport.pkg
Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2010 Data Access Corporation. All rights reserved.
The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.