System Crashing - Memory Issue???

08-14-2003, 12:00 AM
Originally Posted By: Chris Tull<ctull@covcon.com>

Please help!

Here's the situation:

-I'm using VB6, SQL Server 2000, ActiveReports Standard.
-The .exe for the application is set up as a "shell", which has a menu bar
that calls separate User Controls (compiled as .ocx).
-One of the .ocx's is the reporting screen, which contains the ActiveReport
Viewer.

-When the user selects a report and clicks the "Preview" button:

arv.Visible = True
arv.ReportSource = New rptCashReport

Then the report starts:

Private Sub ActiveReport_ReportStart()
strSQL = ...... 'I build a SQL here
dcADO.Source = strSQL
End sub

When the user clicks "Close" on the toolbar:

Private Sub arv_ToolbarClick(ByVal Tool As DDActiveReportsViewer2Ctl.DDTool)
Select Case Tool.Caption
Case "Close"
Set arv.ReportSource = Nothing
arv.Visible = False
End Select
End Sub

-The user can now select a new report, and clicks the "Preview" button:

arv.Visible = True
arv.ReportSource = New rptBonusReport

Private Sub ActiveReport_ReportStart()
...etc.

Now, here is the strange part. I'm developing this under XP and SQL Server
2000 Develper. Everything works fine. I can run multiple complex reports
with no problems. However, once installed at the client site (Windows 2000
/ SQL Server 2000), I can only run one or two reports, and then the entire
.exe crashes (without a warning message) if I try to run another.

Any idea what is happening here?


Re: System Crashing - Memory Issue???

08-15-2003, 12:00 AM
Originally Posted By: Trent Snow - DD<ActiveReports.Support@DataDynamics.com>

Hello Chris--

Are you using anything that would be using a lot of memory for instance any
images or subreports. How much memory is the reports using? Is this
crashing on all 2000 machines or just this one? Is the one particular
report that seems to be using the most memory and is more like to crash?

Are you compiling your reports into an ActiveX DLL?

I have heard some users using DoEvents to force windows to cleanup memory.

Make sure that you set you reports are set to Nothing after you are done
using them.

What gets me is that it works fine on the XP machine are there any major
hardware differences like memory?

"Chris Tull" wrote in message
news:UjWhKCnYDHA.2012@dynaweb.datadynamics.com...
> Please help!
>
> Here's the situation:
>
> -I'm using VB6, SQL Server 2000, ActiveReports Standard.
> -The .exe for the application is set up as a "shell", which has a menu bar
> that calls separate User Controls (compiled as .ocx).
> -One of the .ocx's is the reporting screen, which contains the
ActiveReport
> Viewer.
>
> -When the user selects a report and clicks the "Preview" button:
>
> arv.Visible = True
> arv.ReportSource = New rptCashReport
>
> Then the report starts:
>
> Private Sub ActiveReport_ReportStart()
> strSQL = ...... 'I build a SQL here
> dcADO.Source = strSQL
> End sub
>
> When the user clicks "Close" on the toolbar:
>
> Private Sub arv_ToolbarClick(ByVal Tool As
DDActiveReportsViewer2Ctl.DDTool)
> Select Case Tool.Caption
> Case "Close"
> Set arv.ReportSource = Nothing
> arv.Visible = False
> End Select
> End Sub
>
> -The user can now select a new report, and clicks the "Preview" button:
>
> arv.Visible = True
> arv.ReportSource = New rptBonusReport
>
> Private Sub ActiveReport_ReportStart()
> ...etc.
>
> Now, here is the strange part. I'm developing this under XP and SQL
Server
> 2000 Develper. Everything works fine. I can run multiple complex reports
> with no problems. However, once installed at the client site (Windows
2000
> / SQL Server 2000), I can only run one or two reports, and then the entire
> .exe crashes (without a warning message) if I try to run another.
>
> Any idea what is happening here?
>
>


Re: System Crashing - Memory Issue???

08-15-2003, 12:00 AM
Originally Posted By: Chris Tull<ctull@covcon.com>

Thanks Trent.

Some of the reports are using subreports, but not all of them. None of them
are using images.

I think the crashing issue is related to how I set up the design using the
ActiveViewer. As I stated, the main application is the .exe, it has a menu
bar which calls separate .ocx's. The reporting screen User Control along
with the ActiveReports Designers are compiled into one such ocx. I had
previously included the ActiveViewer on the User Control. This was hidden,
until the user pressed Preview. I would then show the ActiveViewer, and
change the ReportSource. However once a report was running, if you hit the
Close button, it wouldn't stop the process, so I think the issue was more of
a system resource issue than a memory issue. What do you think? I also
noticed that in all of the examples, the ActiveViewer was always placed on a
separate form, as opposed to the way I set it up.

I've decided to not use the ActiveViewer, and instead just use the
"rptReportName.show" method to preview the report in a separate window. Is
this the best way to do this? If so, how can you set this to nothing?

Where are the users using the "DoEvents"?



"Trent Snow - DD" wrote in message
news:JnsP1E1YDHA.1908@dynaweb.datadynamics.com...
> Hello Chris--
>
> Are you using anything that would be using a lot of memory for instance
any
> images or subreports. How much memory is the reports using? Is this
> crashing on all 2000 machines or just this one? Is the one particular
> report that seems to be using the most memory and is more like to crash?
>
> Are you compiling your reports into an ActiveX DLL?
>
> I have heard some users using DoEvents to force windows to cleanup memory.
>
> Make sure that you set you reports are set to Nothing after you are done
> using them.
>
> What gets me is that it works fine on the XP machine are there any major
> hardware differences like memory?
>
> "Chris Tull" wrote in message
> news:UjWhKCnYDHA.2012@dynaweb.datadynamics.com...
> > Please help!
> >
> > Here's the situation:
> >
> > -I'm using VB6, SQL Server 2000, ActiveReports Standard.
> > -The .exe for the application is set up as a "shell", which has a menu
bar
> > that calls separate User Controls (compiled as .ocx).
> > -One of the .ocx's is the reporting screen, which contains the
> ActiveReport
> > Viewer.
> >
> > -When the user selects a report and clicks the "Preview" button:
> >
> > arv.Visible = True
> > arv.ReportSource = New rptCashReport
> >
> > Then the report starts:
> >
> > Private Sub ActiveReport_ReportStart()
> > strSQL = ...... 'I build a SQL here
> > dcADO.Source = strSQL
> > End sub
> >
> > When the user clicks "Close" on the toolbar:
> >
> > Private Sub arv_ToolbarClick(ByVal Tool As
> DDActiveReportsViewer2Ctl.DDTool)
> > Select Case Tool.Caption
> > Case "Close"
> > Set arv.ReportSource = Nothing
> > arv.Visible = False
> > End Select
> > End Sub
> >
> > -The user can now select a new report, and clicks the "Preview" button:
> >
> > arv.Visible = True
> > arv.ReportSource = New rptBonusReport
> >
> > Private Sub ActiveReport_ReportStart()
> > ...etc.
> >
> > Now, here is the strange part. I'm developing this under XP and SQL
> Server
> > 2000 Develper. Everything works fine. I can run multiple complex
reports
> > with no problems. However, once installed at the client site (Windows
> 2000
> > / SQL Server 2000), I can only run one or two reports, and then the
entire
> > .exe crashes (without a warning message) if I try to run another.
> >
> > Any idea what is happening here?
> >
> >
>
>


Re: System Crashing - Memory Issue???

08-27-2003, 12:00 AM
Originally Posted By: Trent Snow - DD<ActiveReports.Support@DataDynamics.com>

Hello Chris--

Can you see if it is one of ActiveReports resources that are getting leaked
by running it through a memory monitoring tool like Numega's.

Whether you use the show or bind the report using the viewer on a separate
form both should give you the same results.

"Chris Tull" wrote in message
news:$PIQIt2YDHA.376@dynaweb.datadynamics.com...
> Thanks Trent.
>
> Some of the reports are using subreports, but not all of them. None of
them
> are using images.
>
> I think the crashing issue is related to how I set up the design using the
> ActiveViewer. As I stated, the main application is the .exe, it has a
menu
> bar which calls separate .ocx's. The reporting screen User Control along
> with the ActiveReports Designers are compiled into one such ocx. I had
> previously included the ActiveViewer on the User Control. This was
hidden,
> until the user pressed Preview. I would then show the ActiveViewer, and
> change the ReportSource. However once a report was running, if you hit
the
> Close button, it wouldn't stop the process, so I think the issue was more
of
> a system resource issue than a memory issue. What do you think? I also
> noticed that in all of the examples, the ActiveViewer was always placed on
a
> separate form, as opposed to the way I set it up.
>
> I've decided to not use the ActiveViewer, and instead just use the
> "rptReportName.show" method to preview the report in a separate window.
Is
> this the best way to do this? If so, how can you set this to nothing?
>
> Where are the users using the "DoEvents"?
>
>
>
> "Trent Snow - DD" wrote in
message
> news:JnsP1E1YDHA.1908@dynaweb.datadynamics.com...
> > Hello Chris--
> >
> > Are you using anything that would be using a lot of memory for instance
> any
> > images or subreports. How much memory is the reports using? Is this
> > crashing on all 2000 machines or just this one? Is the one particular
> > report that seems to be using the most memory and is more like to crash?
> >
> > Are you compiling your reports into an ActiveX DLL?
> >
> > I have heard some users using DoEvents to force windows to cleanup
memory.
> >
> > Make sure that you set you reports are set to Nothing after you are done
> > using them.
> >
> > What gets me is that it works fine on the XP machine are there any major
> > hardware differences like memory?
> >
> > "Chris Tull" wrote in message
> > news:UjWhKCnYDHA.2012@dynaweb.datadynamics.com...
> > > Please help!
> > >
> > > Here's the situation:
> > >
> > > -I'm using VB6, SQL Server 2000, ActiveReports Standard.
> > > -The .exe for the application is set up as a "shell", which has a menu
> bar
> > > that calls separate User Controls (compiled as .ocx).
> > > -One of the .ocx's is the reporting screen, which contains the
> > ActiveReport
> > > Viewer.
> > >
> > > -When the user selects a report and clicks the "Preview" button:
> > >
> > > arv.Visible = True
> > > arv.ReportSource = New rptCashReport
> > >
> > > Then the report starts:
> > >
> > > Private Sub ActiveReport_ReportStart()
> > > strSQL = ...... 'I build a SQL here
> > > dcADO.Source = strSQL
> > > End sub
> > >
> > > When the user clicks "Close" on the toolbar:
> > >
> > > Private Sub arv_ToolbarClick(ByVal Tool As
> > DDActiveReportsViewer2Ctl.DDTool)
> > > Select Case Tool.Caption
> > > Case "Close"
> > > Set arv.ReportSource = Nothing
> > > arv.Visible = False
> > > End Select
> > > End Sub
> > >
> > > -The user can now select a new report, and clicks the "Preview"
button:
> > >
> > > arv.Visible = True
> > > arv.ReportSource = New rptBonusReport
> > >
> > > Private Sub ActiveReport_ReportStart()
> > > ...etc.
> > >
> > > Now, here is the strange part. I'm developing this under XP and SQL
> > Server
> > > 2000 Develper. Everything works fine. I can run multiple complex
> reports
> > > with no problems. However, once installed at the client site (Windows
> > 2000
> > > / SQL Server 2000), I can only run one or two reports, and then the
> entire
> > > .exe crashes (without a warning message) if I try to run another.
> > >
> > > Any idea what is happening here?
> > >
> > >
> >
> >
>
>