VB 6.0's new DataReport designer provides a great way to display
simple datasets. When you use this new tool, however, you may have
found phantom instances of your application cropping up on machines
using the final compiled version. This behavior occurs if you print
the DataReport via code, but don't unload it when you're through with it.
For instance, suppose we added a button to a form with the following code:
Private Sub Command1_Click()
DataReport1.PrintReport
End Sub
and then compiled the project. When you launch the new application,
click the button, and close the application, a phantom instance of
the application shows up in the Windows Task Manager. This phantom
instance results because Visual Basic instantiates the DataReport
object but never unloads it when it's through printing.
To fix this glitch, simply unload the DataReport in the form's
Unload() event, like so
Private Sub Form_Unload(Cancel As Integer)
Unload DataReport1
End Sub
Prevent phantom apps using the DataReport
By James Crowley, published on 14 Jul 2001
| Filed in
You might also like...
VB 6 forum discussion
-
CorelDRAW VBA: cdrTraceLineDrawing FAILS, producing single linear path instead of Centerline trace?
by dancemanj (0 replies)
-
client/server application using activex
by beautifulheart (0 replies)
-
System Error &H8007007E. The specifed module could not be found.
by swiftsafe (5 replies)
-
Invitation to take part in an academic research study
by researchlab (0 replies)
-
Send SMS with SMPP
by mmahmoud (0 replies)
VB 6 podcasts
-
Stack Overflow Podcast: Podcast #45 – Keeping it Sharp
Published 7 years ago, running time 0h54m
Our guest this week is Eric Lippert – language architect extraordinaire and famous for all his work at Microsoft in developing their languages Eric joined Microsoft right out of college and was originally working on VB It’s time for everyone’s favorite game: Name the Worst Feature of that Microso.
Comments