deployment problems with VB6

[NTSGuru]

I have a report that I have written with CR8 to be called from a VB exe.&nbsp;&nbsp;I made the P&D, and installed it to the PC that I want it to run from.&nbsp;&nbsp;Well, the exe works fine, but when the report is called, nothing happens.&nbsp;&nbsp;I cannot get any kind of output from it (printer, window, anything)...&nbsp;&nbsp;I don't want to install the full version of Crystal on that machine.&nbsp;&nbsp;Is there a way that I can get my report to run?&nbsp;&nbsp;Any help would be greatly appreciated.<br><br>TIA<br>Fred

 

[AAP]

I use CR7, this requires a number of DLLs to be available at run-time. Suggest you check the CR8 help files, they should list the required DLLs and their required locations. Exact combination of files will depend on the windows version you are running and exactly what the report is required to do.

 

[NTSGuru]

I did a full package and deploy with my report, which installed all the necessary files for CR8.&nbsp;&nbsp;I don't get any errors when I try to run the report, so I believe that the install went fine.&nbsp;&nbsp;It just does not run the report.&nbsp;&nbsp;Is there a report engine that needs to be installed that I don't know about?<br><br>Fred

 

[emallon]

Fred,
I too am experiencing the same problem. I have no problems developing and testing from my PC. When I P&D the project, install and execute the VB piece runs fine. When I call the report I receive an error from the CPEAUT32.dll file. This is a SCR8 dll.
I will forward this info to Seagate today. I wanted to let you know you are not alone.
Send me your e-mail address. When I get this resolved I will forward you the fix.

Ed.
emallon@estee.com

 

[FowlerConsulting]

Do you have the DSN (Data Source Name) in the ODBC configure on the PC that you are installing the application?

Remember, the report binds to this ODBC data source to run the report.

For Access users that are deploying the .MDB file to the client... make sure that the .MDB file is in the same physical directory as the one it was when you authored the report. If you change this us must 'set location' of the report table/fields to the new location...

Steven Fowler

http://www.FowlerConsulting.com

 

[emallon]

The problem I was experiencing wasn't a DLL error after all. With CR8 it is necessary to open a report before being able to view it(thru VB6). The report I was attempting to open had a subreport embedded within and I wasn't opening the report at the time of execution. Thus, CR8 returned a DLL error when it tried to run the unopened subreport from the open main report. Here's a sample of the code that executes correctly now.
Private Sub cmdReport_Click()
'
Dim SubReport As CRPEAuto.Report
'
On Error GoTo error99:
Screen.MousePointer = vbHourglass
Set CrystalApplication = CreateObject(&quot;Crystal.CRPE.Application&quot
Set CrystalReport = CrystalApplication.OpenReport(strRunReport)
Set CrystalParameterFieldDefs = CrystalReport.ParameterFields
Set CrystalParameterFieldDef = CrystalParameterFieldDefs.Item(1)
CrystalParameterFieldDef.SetCurrentValue (parameterName1)
Set CrystalParameterFieldDef = CrystalParameterFieldDefs.Item(2)
CrystalParameterFieldDef.SetCurrentValue (parameterName2)
Set SubReport = CrystalReport.OpenSubreport(subReport)
Set DbName = CrystalReport.Database
Set DbTables = DbName.Tables
Set DbTable = DbTables.Item(1)
Call DbTable.SetLogOnInfo(my.OraID, &quot;&quot;, my.UserID, my.PassWord)
Set DbName = SubReport.Database
Set DbTables = DbName.Tables
Set DbTable = DbTables.Item(1)
Call DbTable.SetLogOnInfo(my.OraID, &quot;&quot;, my.UserID, my.PassWord)
CrystalReport.Preview
Screen.MousePointer = vbDefault
'
Exit Sub
[sig][/sig]

 

[Hawkes]

I can't get an answer from Seagate as my problem is similar. I have native (DSN-less) reports that I have deployed (as I thought this would be easier to deploy). On testing them in my development area I have no problem at all and changing the locations and connections in code isn't a problem either.

However, when I deploy these reports on site the reports on opening error as they are still trying to connect to their original location first BEFORE the code changes them to the users server login and table locations.

The only way I got round this at the moment was to MANUALLY change the reports table locations and logon info.

The only other way I could get round it is to change them all back to ODBC and get the code to create a default ODBC connection that is used by all the reports.

Gazza [sig][/sig]

 

[NTSGuru]

I finally have a solution after a LOT of going back and forth with Seagate. It seems that there needs to be a SQL client installed on the deployed machines. You don't have to have full install of SQL installed on the target machines, but just the &quot;SQL client&quot;, which can be found on the MSSQL install CD. Once that is done, and a full P&D has been performed, then CR8 runs perfectly.

HTH
Fred [sig][/sig]