Considerations when using the export functions
The export functions are complex function calls. To avoid errors when exporting report files from your application, keep the following things in mind:
- In order to use PEGetExportOptions and PEExportOptions, you must be using the version of the Crystal Report Engine (CRPE32.DLL) that came with the Professional Edition of Crystal Reports. If you have an earlier version of CRPE32.DLL installed on your machine and its earlier in the path, the program may find it first and not find the export functions. This can happen particularly if you are upgrading to the Professional Edition of Crystal Reports from the version of Crystal Reports that was shipped with Visual Basic Professional Edition. Visual Basic included an earlier version of CRPE32.DLL. Search your disk and delete or rename earlier versions of CRPE32.DLL, or make appropriate adjustments to your path statement.
- Make sure all format DLLs and destination DLLs are located in the same directory as CRPE32.DLL. Once Windows finds CRPE32.DLL, it will expect all of the DLL files to be in the same directory. Format DLLs are all UXF*.DLL files and Destination DLLs are all UXD*.DLL files. As a general rule, it is best to keep all of these files in the \CRW directory or the directory into which you installed Crystal Reports. Also, make certain that the PATH statement in your AUTOEXEC.BAT file includes \CRW.
- The UXF*.H and UXD*.H header files are only necessary when compiling your application. These files should be copied to the same directory as your application's source files.