Crystal Reports / VB6

Question

3.00/5 (1 vote)

See more:

There are thousands of posts referring to the issues of exporting Crysatl reports to PDF via VB.

I have read most of them "missing or out of data export dll", but none of the solutions posted seem to work.

Does anyone have a working solution - I use Crystal 8.5 with Crystal Viewer and am running reports of an ADO recordset, but the view works fine - as does export to Word and RTF. Have tried V 10 also but Crystal seem to change their goalposts with each version so the code required changes each time.

Nightmare!

Steve

I am distributing exportmodeller.dll, crtslv.dll, crxf_pdf.dll together with all the usual u2*.dll files.

Posted 17-Mar-12 20:00pm

steveRRRRRRR

Add a Solution

Comments

Pete _BSC 27-Mar-12 13:39pm

I ran into a similar issue where exporting to PDF did not work. I was missing the exportmodeller.dll and crtslv.dll. For the 3 files you listed, what are the version #'s on them? Here are mine:

ExportModeller.dll
C:\Program Files\Common Files\Crystal Decisions\2.0\bin
%CommonFiles%\Crystal Decisions\2.0\bin
Monday, July 28, 2003 - 03:54:44 PM
Product Version: 8.6.2.661
File Version: 8.6.2.440

crtslv.dll
C:\Program Files\Common Files\Crystal Decisions\2.0\bin
%CommonFiles%\Crystal Decisions\2.0\bin
Friday, July 25, 2003 - 01:32:18 PM
Product Version: 8.6.1.726
File Version: 8.6.1.726

CRXF_PDF.DLL
#WinDir#\crystal
%WinDir%\Crystal
Friday, July 25, 2003 - 02:22:40 AM
Product: 8.6.2.660
File: 8.6.2.429

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)