Refreshing Crystal Rpt

[Jefftopia]

I use Crystal Rpt 8.0 via the Report Design Component in Visual Basic 6.

I am using the following method for calling up my reports:

With frmRptView
        .Show
        .CRViewer1.ReportSource = rptPrimDls3
        .CRViewer1.ViewReport
    End With

frmRptView is a form I use to call up all of my reports. The only thing on it is the CRViewer1 control.

My problem is that the report is not refreshing accordingly. If the user makes a change to the underlying table, which the report is based on, and then goes into view the report the change will not be reflected. It is only after the user exits the application and returns that the change will appear in the report.

Note: Doesn't seem to matter if I have the report set to 'Verify on Every Print' or not.

Thnx

[ARPRINCE]

Have you tried adding....

crviewer1.refresh

if that does not work, try modifying the method you use to call your report. Usually, in all reports that "I" have encountered so far, you have this part (see 2 lines below) inside the form - frmRptView (Form_LOAD) itself. If you have it already, then try removing the 2 lines in your code.

.CRViewer1.ReportSource = rptPrimDls3
.CRViewer1.ViewReport

In my case, I usually just call the form and the report comes up.

frmRptView.Show 'YOU WILL BE LOADING THE FORM TO BE VIEWED ON THE SCREEN. ALL 
'CRYSTAL RELATED EVENTS SHOULD BE PLACED 
'OR INITIALIZED WITHIN THE FORM ITSELF.

[Jefftopia]

I tried adding CRViewer1.Refresh as suggested and received a Run-time error: Method 'Refresh' of object 'ICrystalReportViewer3' failed.

Until I can figure something else out, I set EnableRefresh button property to True. Now my users will have to use this button to update their report. Why can't I do what this button in Crystal Reports is doing in vb?

[VB4fun]

not quite sure here...

is this a typo ?

object 'ICrystalReportViewer3'

do you somehow have more than one object on the page? Because everywhere else I am seeing CrystalReportViewer1...

[brucevde]

ICrystalReportViewer3 is a Crystal COM object.

These types of errors are usually caused by an invalid installation or corrupt registry. One or more of the crystal dlls may not have registered properly or could be the wrong version.

I am suprised the Refresh button on the Viewer control works.

[Avatarp]

I get the same error when I try to refresh my Viewer programmatically

CRViewer1.Refresh

so where is the solution for this issue?

[RobDog888]

See this other thread that I answered.

CR Refresh

[tommygrayson]

I use Crystal Rpt 8.0 via the Report Design Component in Visual Basic 6.

I am using the following method for calling up my reports:

With frmRptView
        .Show
        .CRViewer1.ReportSource = rptPrimDls3
        .CRViewer1.ViewReport
    End With

frmRptView is a form I use to call up all of my reports. The only thing on it is the CRViewer1 control.

My problem is that the report is not refreshing accordingly. If the user makes a change to the underlying table, which the report is based on, and then goes into view the report the change will not be reflected. It is only after the user exits the application and returns that the change will appear in the report.

Note: Doesn't seem to matter if I have the report set to 'Verify on Every Print' or not.

Thnx

Try using CRViewer1.RecordSelectionFormula on your parameter so that every time a user presses the refresh button the report will look to the valu in the recordselectionformula.

[fabehamobile]

you can refresh your report by closing the odbc connection before calling this code.

I use Crystal Rpt 8.0 via the Report Design Component in Visual Basic 6.

I am using the following method for calling up my reports:

With frmRptView
        .Show
        .CRViewer1.ReportSource = rptPrimDls3
        .CRViewer1.ViewReport
    End With

frmRptView is a form I use to call up all of my reports. The only thing on it is the CRViewer1 control.

My problem is that the report is not refreshing accordingly. If the user makes a change to the underlying table, which the report is based on, and then goes into view the report the change will not be reflected. It is only after the user exits the application and returns that the change will appear in the report.

Note: Doesn't seem to matter if I have the report set to 'Verify on Every Print' or not.

Thnx