|
-
Jun 14th, 2003, 11:05 AM
#1
Thread Starter
Hyperactive Member
CR9 export to PDF
I have tried and tried to work through a printer issue (see thread CR9...easier????) And now CRDecisions is telling me to export to PDF and try that issue.
Has anyone done this successfully, without hours and hours of frustration?
I am distributing an app with acrobat reader already a part of it, Using VB6 and CR9.
I am wondering what kind of advice anyone can give on exporting exsisting .rpt files to PDF format, so the end users can print (no matter what the printer is) and have a success.
Ideas?
-
Jun 16th, 2003, 11:35 AM
#2
I read the other post but sorry I can offer no help.
I don't have CR9, the following code to export to pdf was written for version 8.5.
VB Code:
Dim objApp As CRAXDRT.Application
Dim objReport As CRAXDRT.Report
Dim objExportOptions As CRAXDRT.ExportOptions
Dim objTable As CRAXDRT.DatabaseTable
Set objApp = New CRAXDRT.Application
Set objReport = objApp.OpenReport("d:\testing\report1.rpt")
With objReport
For Each objTable In .Database.Tables
'set the login information for SQL server or Oracle.
objTable.SetLogOnInfo ...
Next
Set objExportOptions = .ExportOptions
With objExportOptions
.DestinationType = crEDTDiskFile
.DiskFileName = "D:\Testing\Report.pdf"
.FormatType = crEFTPortableDocFormat
.PDFExportAllPages = True
End With
.ReadRecords
.DisplayProgressDialog = False
.Export False
End With
Set objTable = Nothing
Set objExportOptions = Nothing
Set objReport = Nothing
Set objApp = Nothing
-
Jun 16th, 2003, 11:52 AM
#3
Thread Starter
Hyperactive Member
Thanks for your reply,
Dont suppose you have some advice on the DLL's...?
I havent made it far enough to deploy the app with the export part..but from what I am reading...the DLL's are frustrating if you dont know exactly which ones and have no control over the registration..
I am using VB6, CR9...and will be having people load my app at other locations, thus manually registering is not an option for this situation...
Any help or advice would be greatly appreciated.
-
Jun 16th, 2003, 12:43 PM
#4
the DLL's are frustrating if you dont know exactly which ones and have no control over the registration..
You are right, people seem to have problems installing the run-time files for Crystal.
Fortunately, I have never experienced these issues. The information you need is in the RunTime.hlp file. It tells you exactly which files need to be installed. Just take the time and care to investigate which dependancy dlls are required, especially if your app is going to be installed on multiple OS.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|