"Server has not yet been opened" using SQL Designer File

[PeteCozens]

I have an automated process which runs reports overnight, and exports them as Crystal Report files (this way, the data is saved with the report, therefore the client PCs do not need database connections).

When the report is loaded by the client app (written in VB6, using the Crystal 8.5 RDC Viewer), I get the error "Server has not yet been opened", but only for reports which are based on Crystal SQL Designer files. Any ideas why? The VB Code is as follows:

Dim objCrystal As New CRAXDRT.Application
Dim objReport As CRAXDRT.Report
Set objReport = objCrystal.OpenReport(strReportPath)

objReport.DisplayProgressDialog = False
objReport.EnableParameterPrompting = False

CRViewer1.ReportSource = objReport
CRViewer1.ViewReport

Thanks for any help,

Pete

 

[Guest_imported]

I have an automated process which runs reports overnight, and exports them as Crystal Report files (this way, the data is saved with the report, therefore the client PCs do not need database connections).

When the report is loaded by the client app (written in VB6, using the Crystal 8.5 RDC Viewer), I get the error "Server has not yet been opened", but only for reports which are based on Crystal SQL Designer files. Any ideas why? The VB Code is as follows:

Dim objCrystal As New CRAXDRT.Application
Dim objReport As CRAXDRT.Report
Set objReport = objCrystal.OpenReport(strReportPath)

objReport.DisplayProgressDialog = False
objReport.EnableParameterPrompting = False

CRViewer1.ReportSource = objReport
CRViewer1.ViewReport

Thanks for any help,

 

[PeteCozens]

?

 

[StevenK]

I've seen this message "Server has not yet been opened" on a number of occasions when developing applications against Crystal Reports (I use SQL Server 7.0 and Delphi 5).
Ensure that the Dll's are registered for the 'CRViewer' component if you are making use of this - although you would get an error regardless of the report you were attempting to view - not just specific ones.
The other suggestion would be to ensure that the client machine has the required database access DLL's. Again I would have thought this would have raised an error regardless of the report.
What it might come down to is the fact that you are NOT passing the appropriate log-on information for the data tables that the report is accessing.
In the case of SQL Server 7.0 from Delphi I need to pass parameters to indicate the server-name, database-name, table-name(s), user-name and password.
Hope that this helps.
Steve