Crystal Reports - Physical database not found

I recently installed crystal reports 8 replacing crystal reports designer component 6.0. After packaging my application and installing it on a client, I get "Physical database not found" when I try to print reports. I don't get this on the system that I created the application with or with the old report designer component.

Am I missing a dll or something when packaging?

Thanks in advance

Sounds like the path of the database you are trying to access is not correct or not availabe on the clients PC

The client has the same drive mappings as my development system. The database is Visual FoxPro 5.0 but I don't think that matters and I don't think it's my code but here it is anyway.

Dim rstCurrent As ADODB.Recordset
Dim strSql As String
Dim Report1 As rptAdjuster

Screen.MousePointer = vbHourglass

strSql = "SELECT TRIM(Adjuster.adj_last)+', '+ TRIM(Adjuster.adj_first) as Name, Adjuster.client_num, Company.comp_name, Company.city "
strSql = strSql & "FROM openclose!company INNER JOIN openclose!adjuster "
strSql = strSql & "ON Company.comp_id = Adjuster.comp_id ORDER BY name"

Load frmReport

Set rstCurrent = New ADODB.Recordset
rstCurrent.Open strSql, fCnn1, adOpenForwardOnly, , adCmdText

Set Report1 = New rptAdjuster

Report1.Database.SetDataSource rstCurrent

frmReport.crvCommon.ReportSource = Report1

frmReport.crvCommon.ViewReport

frmReport.crvCommon.Visible = True

frmReport.Show

Screen.MousePointer = vbDefault

Quote:

---

Originally posted by dcarlson
I recently installed crystal reports 8 replacing crystal reports designer component 6.0. After packaging my application and installing it on a client, I get "Physical database not found" when I try to print reports. I don't get this on the system that I created the application with or with the old report designer component.

Am I missing a dll or something when packaging?

Thanks in advance

---

Solution to the "Physical database not found" error

Hi ! Of course you are going to get this message with the last release of the RDC. I experienced this problem and solve it the way I'm going to suggest to you.

FIRST: Make sure you do not use the Report.Database.Verify
method in your code and if so, comment it out.
Because this will cause the engine to try to
located the source database in the location you
specified at design time.

SECOND: Make sure you add this requiered Dlls when
packaging the solution with the Package and
deployement Wizard or anything else:

Msvcrt.dll
Msvcirt.dll
Msvcp60.dll

TRY THIS AND LET ME KNOW at: [email protected]

Thanks, but I already fixed it. I haven't checked it out in a while but I think that you just need to include the msvc60.dll in the package.